As a large organisation with several independent product verticals, we need the ability to lock down account-level customizations (e.g. layouts, custom fields, workflows) by owner (+ collaborators) so that we can retain adequate controls without l...
Joe Buehlmeyer
almost 3 years ago
in Account settings
0
Future consideration
Update JIRA integration when feature ranking changes in Aha
I have a Aha to JIRA integration set up which allows me to prioritise features in Aha by a combination of Rank and Score. We frequently re-prioritise cards in Aha (therefore changing the rank) but this doesn't trigger an update in JIRA. I rarely c...
Guest
almost 6 years ago
in Jira
6
Unlikely to implement
Adding a legend to the Gantt Chart would help people viewing the chart to understand what the color of each bar means, especially if they are seeing it for the the first time. Currently if you make a custom roadmap and put it in a presentation a l...
Kyle Cleveland
over 3 years ago
in Reports
0
Future consideration
ability to duplicate a story map if want to show different versions- similar to duplicating features.
goal of feature is to be able to work off different versions/drafts of the map.
C K
over 5 years ago
in User story map
1
Unlikely to implement
If I want to manage (e.g. replace tags by others) my custom field choices (of type predefined tag list) I need to search a long time because they are not sorted alphabetically. Please sort them alphabetically.
Promoting an Idea to Feature, Master Feature, Initiative should carry over many-to-many custom field values like other custom field types
Just like Custom field values will transfer from ideas to Feature/Master Features/Initiatives when promoted assuming a custom field with the same Key name exists in both, the same should occur with many to many custom fields as well. My use case i...
Matt Case
over 8 years ago
in Ideas
2
Already exists
It would be useful to define default Document Access settings for notes/whiteboards at parent line levels to be inherited down to workspaces instead of needing to make setting changes for each workspace individually
Jeanette Resnikoff
over 1 year ago
in Notes / Whiteboards
0
Future consideration
What is the challenge? For data quality, we want to notify an Epic/Feature creator when then have forgotten to tie the record to an Initiative, Objective, or Key Result What is the impact? Work that should be tied to these is not visible, monitore...
Lorena Connolly
7 months ago
in Features
0
Future consideration
What is the challenge? Document metadata that needs to be part of the document content must be manually entered and updated. For example, a document's last modified date or a document's custom field reflecting a feature's lifecycle state (e.g., be...
David
7 months ago
in Knowledge base
0
Future consideration