Sync record's workspace, goal, initiative, epic, and release (name and link) to integrations
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker
almost 7 years ago
in Jira
14
Shipped
Ability to filter reports dynamically in the dashboard. For example, apply an initiative filter to all reports in the dashbaord so I don't have to create multiple dashboards showing the same information for different initiatives.
Automation actions to have 'same as' to copy field values
Currently if I need pass on a field value from one field to another, there is no easy way, but to create separate automation rule for each value. Which is not optimal and will have to create 10 rules for 10 values and if a new value is entered nee...
Jyothirmayi Talaparthy
over 4 years ago
in Application
14
Shipped
Ability to create release phases and milestones which automatically use business days
For example, this would allow me to create week-long phases which would be 5 days (and not 7 days). A milestone would also automatically be populated on the first business day available.
Related to this, I would like to be able to create templates...
As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release
Ideas portals should not show ideas from other portals that share the same products
If you create two private (or public) ideas portals and both have product A and product B, any ideas created in either portal are visible in the other.
In this scenario, I want one portal for employees and one for customers. I do not want custome...
It would make the Starter roadmap much clear to read when you could show the Master features in Releases instead of individual features. So please add possibility to display also the Master releases
Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match
If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...