RELATED IDEAS
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 when looking at the requirement list but a new requirement custom field (called Priority) is and I would prefer to see that information when looking at the collapsed requirement list than the status.
3
MERGED
Improve requirements grooming in a feature.
We roll up feature story points from requirements estimates. The story points are linked to JIRA so are updated by teams over time. This works great, but you have to expand the requirement in Aha! to see the individual requirement estimates which ...
0
Future consideration
1
MERGED
Customize information shown on the requirement line within a feature
It would be really helpful if we could choose what information is displayed on the summary line of the requirement when viewing all the requirements in a feature. There are a couple of key pieces of additional information I would ideally like to b...
0
Future consideration
3
MERGED
3
MERGED
Add custom Requirement fields to Feature card
I'd like to be able to set a due date custom field for requirements and be able to add that to the feature card, so I can see it with the current status. Sometimes knowing "In Development" isn't enough and I need to understand exactly how far alon...
0
Future consideration
3
MERGED
Choose Quick View Data for Requirements
Right now you can only see Requirement Name & Status. It's important for us to also see assignee at quick glace (like in JIRA), without having to click into the record. Would love to be able to select what you can see in the form.
0
Future consideration
Agree. We would love to be able to include the reference number from another application such as DevOps (we use a custom field for this which you can only see when it's expanded), the estimation/story points allocated or MOSCOW rating.
We workaround this at the moment by including this extra information in the title of the requirement, but requires inputting this in twice (once in the field available when expanded then again in the title).
Agreed! The ability to customize the requirements list in a feature would be HUGE. We integrate Aha! with Pivotal Tracker and are pushing our Features to Pivotal as epics and Requirements as user stories. Our process is to begin our epic and story development within Aha and push to Pivotal once they've been reviewed and approved. Unfortunately, the way that list view works is kind of clunky. That view within the epic is where we live every day while we're working on our stories, so it'd be great to get some customization help. Also amazing would be to allow us to make edits to the requirements right within that list as we're working on the epic.
Very important for us to be able to see & report on assignee
I agree that this area should be customizable since being able to see the relevant data at a glance is beneficial.
We would like to add the Requirement number in TFS, which we also have as a custom field. We have an integration from Aha! to TFS, so to be able to quickly see the TFS number for a Requirement would be a big value for us,