Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 262

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...
Ann L almost 3 years ago in Jira 0 Future consideration

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...
Jonathan Shaw over 1 year ago in Jira 0 Future consideration

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.
David Strathy-Miller almost 3 years ago in Jira 0 Future consideration

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...
Guest about 10 years ago in Jira 1 Already exists

If a comment is deleted in Jira, please delete that comment in Aha! also

Some comments are for testing purposes or are not correct. If we have decided to delete a comment from an epic or story in Jira, we would like it to be removed from the feature in Aha! as well.
Kelly Sebes over 6 years ago in Jira 1 Will not implement

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...
Anh Truong over 3 years ago in Jira 1 Future consideration

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...
Justin Woods about 5 years ago in Jira 0 Future consideration

Persistent filters for integrations and incoming product updates

Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest about 6 years ago in Jira 0 Future consideration

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...
Guest 9 months ago in Jira 0 Future consideration

Show comments added in JIRA as part of a state transition.

Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA. This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi over 5 years ago in Jira 2 Future consideration