Skip to main content
All CollectionsGetting Started with Upright ListerGetting Started
Feature Requests and How They are Prioritized
Feature Requests and How They are Prioritized

How to share ideas on ways to improve Lister and Link

Rain Gilbert avatar
Written by Rain Gilbert
Updated over a year ago

Overview

We love hearing from our customers on the ways we can improve Lister and Link! When planning out new feature development, we reference the requests received from our customers. This article will outline how to request new features and how we prioritize them.


Table of Contents


How to Request a Feature

  1. Click the question mark icon in the top right navigation menu in Lister

  2. Select "Request a feature"
    ​

    How to start a feature request in Lister
  3. Fill in the title and description in the "Create a Post" box on the left describing the feature you'd like us to implement in Upright Lister

  4. Optional: Upload a picture to add additional context to your feature request

  5. Click the blue "Create Post" button

    How to start a feature request in Lister

How to Up-Vote & Leave Comments on Existing Features

If the feature you're looking to request already exists in our system, we'd love to hear your thoughts as well!

  1. Vote for features posted by other users by clicking the up arrow next to a post

  2. Leave comments on an already requested feature by clicking the comment bubble on the right of the post
    ​

    How to upvote and add a comment to a feature request
  3. Type your comment in the box and click 'Submit' once you've completed your comment
    ​

    How to upvote and add a comment to a feature request

Comments on why a feature is useful and the problem it solves for you are extremely helpful to our team!


How Feature Requests Are Prioritized

There are a number of factors that are considered when it comes to prioritizing feature requests. Here are some of the factors we take into consideration when evaluating which features to work on next (not necessarily in this order):

  • Technical Complexity: How easy or hard it is to build out from a technical perspective and what else within our system would be impacted

  • Timeline: How long it will take to build it out, and how much planning is required

  • Impact: How many customers need/want it and how beneficial it would be to the workflow of our overall customer base

  • Existing Workarounds: Does a workaround exist that fits the need? If so, a feature may be de-prioritized in favor of others with no suitable workaround

Our team typically has about one to two month's worth of features planned out in advance. There is often some wiggle room where we can squeeze in smaller features of lower complexity, but we do try to plan out as far in advance as possible.


Related Guides

Have questions? Reach out to us at support@uprightlabs.com or via chat anytime between 9am-6pm ET, Monday to Friday


​

Did this answer your question?