New ideas/features lists do not remember my customizations
When I go back to the ideas list I expect that it will remember the changes I made to the columns and filters. I believe it used to, but the new version of them does not.
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
almost 4 years ago
in Features
1
Future consideration
When using a date range picker tab should advance from the start date to the end date
What is the challenge? Tab advances to next field, not end date What is the impact? I have to jump from keyboard entry to mouse. Other fields cycle on tab. Describe your idea when in first date, tab should jump to end date.
Guest
5 months ago
in Features
0
Future consideration
Allow re-ranking requirements on a feature by status
As I work through the requirements on a large feature, I find it useful to keep them sorted by status, so I can have a focused group of items that still need my attention. It would be nice to automate this sorting via a rerank button, similar to t...
Zach Schneider
almost 7 years ago
in Features
0
Future consideration
Who would benefit? All Users What impact would it make? Save lots of time How should it work? If you have 30 releases already released like we have, you have to scroll multiple times to the right every time you open the page to get to the newest r...
Allow to create multiple feature boards where columns can be defined by a different set of criteria. For example, I want to have one in a Kan-Ban style (with swimlanes https://big.ideas.aha.io/ideas/APP-I-4228 by a release) , another one with a co...
Anton Mamichev
over 7 years ago
in Features
1
Unlikely to implement
Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
Steven Schafer
over 1 year ago
in Features
5
Unlikely to implement
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
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