What is the challenge? I work with two large teams across a big product portfolio. Any given week, I can have engineers assigned to multiple features. When I go to assign the next feature, I don't have any contextual information about the other wo...
Nathaniel Collum
5 months ago
in Features
0
Future consideration
Ability to customize the list of requirements within a feature
Currently, the list of requirements within a feature is fixed and only contains 3 columns:
Requirement #
Requirement Name
Status
It would be great if we could customize the columns to display. In my case, the status is not that important to see ...
Pascal Begin
over 7 years ago
in Features
7
Future consideration
Will not implement status should not show on priority list
What is the challenge? Trying to keep an accurate priority list What is the impact? Priority list for stories/features Describe your idea Only stories/features that you are actually going to do should be on the priority list. Not will not implemen...
When working on lengthy proposal or documentation, it would be nice if you could collapse certain sections of the text editor to keep the description cleaner. My use case is when presenting an analysis — but I don't want ever table showing at all ...
Micaela Wright
over 3 years ago
in Features
0
Future consideration
Add "release phase" as an updatable field on the feature card.
I'm using release phase as my "sprints". When creating features, sometimes I want to add them directly into the sprint as they are being created. Right now it is a bit arduous to not have that field at my finger tips when creating features with th...
Amy Flower
over 3 years ago
in Features
4
Future consideration
Automation of related record (Feature) updates the "parent" Record (Feature)
The work request option is great and one of the main functions we utilize to connect dependent work across programs. The only issue we see with this is that the parent record, in our case a feature, does not get updated when the "related" record i...
Danielle Martinez
over 1 year ago
in Features
4
Future consideration
Restore the remaining estimate when a Requirement is moved from Shipped back to In Development
When a Requirement is shipped the remaining estimate will go to 0, but if that Requirement is re-opened then it will stay 0. Is there a way to restore the remaining estimate when a Requirement is re-opened?
Dale Crane
about 2 years ago
in Features
3
Future consideration
It would really helpful if I could reorder releases on the features board. I often work on multiple different projects simultaneously. And often there are parts we can release within project before everything else is done. So, we create multiple r...
Guest
over 9 years ago
in Features
5
Unlikely to implement
When we review features with stakeholders, we need to consider and refine both the description (user problem) and the acceptance criteria (definition of done) before it can be approved. We also need the acceptance criteria to sync to an equivalent...
Brent Schumann
over 3 years ago
in Features
1
Future consideration