Jira
Sort by:
Trending
Status:
Showing 263
15
VOTE
Deleting a feature or requirement should delete the linked Jira issue(s)
When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...
11
Will not implement
2
VOTE
JIRA Integration - Allow Changing Board
We recently had to migrate JIRA tenant to another existing one (as the result of an acquisition). Whilst I was able to just change the server address and the integration URLs pointed to the correct location of the migrated issues, the board used f...
0
Future consideration
4
VOTE
Jira integration - pre filter based on tag/field
Often there are items on a roadmap that do not require Engineering work. However when a release is sent to Jira (or over dev system) all the items under that release are also sent. This means that the down stream system can become full of items in...
0
Future consideration
1
VOTE
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
0
Future consideration
4
VOTE
5
VOTE
Support Movement of Requirements to Different Features in Other Workspaces
We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
1
Future consideration
9
VOTE
14
VOTE
When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog
When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...
1
Already exists
7
VOTE
Allow child integrations to inherit the "run-as" user from an integration template
The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism.
The integration template functionality allows settings from a master template to be adopted by child int...
0
Future consideration
2
VOTE
Sync Delivery Risk manual flag to Jira "Flagged"
In Aha!, if you have enabled 'Delivery risks', one of the things you can do is manually set a flag on a Feature (or Epic or Requirement). In Jira, you can also 'Flag' issues similarly. Aha!: https://www.aha.io/support/roadmaps/strategic-roadmaps/c...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved