Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 210 of 7169

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

Deleting a JIRA issue (story, epic) that is linked in AHA, should be deleted in AHA

When you have items linked from JIRA to AHA (example STORY->FEATURE, EPIC->MASTER FEATURE), the items deleted in JIRA should be deleted in AHA
Carlos Palminha over 2 years ago in Jira 6 Will not implement

Add support for Jira Portfolio "Team" field

Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
Scott McLean about 2 years ago in Jira 1 Future consideration

Update API integrations with JIRA to add Created Date and Resolved Date

We would like to be able to map the created date as well as the resolved date to fields within aha from JIRA.
Guest about 1 year ago in API / Jira 1 Future consideration

When sending an Epic to Jira, allow sending of all /updates to Features

Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...
Karie Kelly 3 months ago in Jira 0 Future consideration

Support for Jira Embedded Images

Jira tickets support embedded images using the following format. !ImageURL! for example: !https://imageurl.png|width=50%,height=auto! Jira Image Formatting Notation We make very heavy use of this feature to pull our designs into the jira tickets...
Guest about 5 years ago in Jira 1 Future consideration

Support JIRA issues being unassigned

If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Danny Archer over 6 years ago in Jira 2 Future consideration

When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.

The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin almost 4 years ago in Jira 5 Future consideration

Update JIRA integration when feature ranking changes in Aha

I have a Aha to JIRA integration set up which allows me to prioritise features in Aha by a combination of Rank and Score. We frequently re-prioritise cards in Aha (therefore changing the rank) but this doesn't trigger an update in JIRA. I rarely c...
Guest over 3 years ago in Jira 3 Future consideration

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko about 1 year ago in Jira 1 Future consideration