Current burndown charts (release > details) are created at the release level. It would be great to be able to customise the burndown to view progress at a release phase level. We would love to be able to review progress at the release phase lev...
Daniel Scudds
about 7 years ago
in Releases
1
Unlikely to implement
We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.
We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...
Wen-Wen Lin
about 5 years ago
in Jira
1
Future consideration
Option to ignore changes to Items that AHA does not know about.
We have joined Azure Dev Ops to Aha via the integrations.
In fact there will by 7+ Integrations due to the size of the portfolio.
We have restricted the webhooks so that:
New / Updates to (Release / Epic Work Item types) are pushed to AHA from ...
Guest
about 5 years ago
in Integrations
0
Future consideration
Currently, we are using a Rank column which is a # field but doesn’t automatically rank the other records. Can we add a rank functionality in custom tables to avoid updating individual records. Ex. if we have 100 records and ranked them 1-100, if ...
Vlad Spector
about 4 years ago
in
0
Future consideration
Who would benefit? Any team in a SAFe model What impact would it make? A roadmap for each team in one big table with a row for each team. They could draw red lines between different stories/features to indicate depedencies How should it work? See ...
Who would benefit? everyone What impact would it make? wouldn't cut out potentially critical info How should it work? when exporting an Idea (both in .pdf and .png) some info in the right side column of the export is cut off. This should not happe...
Workspace name is removed from a sub-release in the Release Gantt
Who would benefit? Those using Roll Up releases What impact would it make? It would improve clarity How should it work? This is really a bug - often when the sub-release is expanded the workspace name is removed. It should persist.
Guest
about 1 year ago
in Releases
0
Future consideration
Our organization doesn't need the added hierarchy of initiatives. We want to remove the option to promote an idea to an initiative, so users of our workspaces won't accidentally do so.
Asim Dhital
about 3 years ago
in Ideas
0
Future consideration
We have multiple paid seat groups that represent each of our different business units which allows us to delegate the administration of paid seat licenses. Each seat group has maxed out their allocations and we have no unused licenses. The issue i...
Joe Granville
about 4 years ago
in Account settings
2
Future consideration
As a product manager I'd like to be able to define both an internal and an external product name.
The case might be that our team and internal employees refer to a product as "X". Externally, our customers know the product as "Y" in marketing and ...
Scott Goldblatt
about 8 years ago
in Ideas
5
Already exists