ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 231

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox about 2 years 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 mean...
Michael Buonassisi almost 4 years ago in Jira 2 Future consideration

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 about 5 years ago in Jira 1 Will not implement

Add Product Name to JIRA Integration

The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin almost 4 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 over 4 years ago in Jira 0 Future consideration

Integrate Master Features and related features to different JIRA projects

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
Guest 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 in...
Justin Woods over 3 years ago in Jira 0 Future consideration

Ability to update a file attachment of a feature and update in the linked record of JIRA as well

Hi - We have Aha! - Jira integration where our features are mapped to JIRA stories. Features also have several file attachments which get propagated to JIRA stories. However, our Product Managers need to update the file attachments. Currently ther...
Michael Zadda over 5 years ago in Jira 1 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 over 8 years ago in Jira 1 Already exists

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...
Guest over 8 years ago in Jira 11 Will not implement