All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5654
1
VOTE
Make record ID's distinct for records shared with Develop team
When users are notified of Product features that are assigned to a Develop team, the notifications link the users to the Roadmaps board where it originated. On the reverse, Develop features that get assigned to a Roadmaps release, direct users to ...
0
Future consideration
2
VOTE
Segmented progress bar on epics and features
Would be great to have the progress bar not just calculate on some field completed, but also show as a sort of segmented progress bar, where you can see the percentage of items in another status category. This would allow to have in one view a cle...
0
Future consideration
2
VOTE
Dependency Report - Provide columns on Primary record instead of concatenating the fields together
On the dependency report - we often want to put the AHA feature ref ID; the name of the feature and add a tag. Providing more than one piece of information to make it useful to the user as they view the dependencies to the related records that can...
0
Future consideration
2
VOTE
4
VOTE
History of items created via integration
In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
1
Future consideration
1
VOTE
The ability to create a report to show if there are any pending Integration Updates rather than having to manually look for them
Simplify the ability to know if there are pending updates to either Import or Ignore by running/scheduling a report with this data by Workspace and Integration, etc.
0
Future consideration
1
VOTE
Collaborators on a presentation should be able to edit and save a view
When a report/view is added to a presentation, any collaborator for that presentation should be able to edit the views on the slides. Right now, only the creator of the view can edit and save. All other collaborators must save a copy of the view i...
0
Future consideration
1
VOTE
4
VOTE
Integrations 2.0: Allow Master Feature relationship for Requirements
I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...
0
Future consideration
3
VOTE
© 2025 Aha! Labs Inc.•All rights reserved