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
The AI feature allows us to generate acceptance criteria in Gherkin format; currently the syntax highlighting option for blocks allows a user to select a variety of programming languages, but not Gherkin. I figured that would be a relatively easy ...
Guest
over 1 year 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
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
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
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
Allow customized scorecard to be used for prioritization view within a workspace.
As an organization, we have different groups that need to use a customized scorecards. The new prioritization view is useless without the ability to select a scorecard that is unique to your group. If I change the current Account Product Value sco...
Doug D
about 2 years ago
in Features
2
Future consideration
It would be great if we could use an Automation rule at the feature level to update the status of related ideas. Currently, it is possible to update ideas which were promoted to the feature, however, ideas simply "related" are not updated. I would...
Shawn Zenz
over 4 years ago
in Features
1
Future consideration