Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 238

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 2 years ago in API / Jira 1 Future consideration

Urgent Jira Integration Needs: Resolution, Resolved Date & Percent complete

These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...
Marcie Gardner over 1 year ago in Jira 2 Future consideration

Automatically create/update Notification Groups based on location hierarchy

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...
Guest over 1 year ago in Jira 0 Future consideration

Be able to map to a persona name value with JIRA integration

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping
Barnett Klane about 4 years ago in Jira 3 Future consideration

Map JIRA Fix Version to Aha Release Phase

We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key ...
David Vins almost 5 years ago in Jira 8 Future consideration

Provide error if the Jira webhook "Exclude body" checkbox is selected

When configuring a webook in Jira, there is a checkbox: ☐ "Exclude body" Request with empty body will be sent to the URL. Leave unchecked if you want to receive JSON. If someone accidentally checks that, Aha! won't get any updates. There is no log...
Emily Yankush 11 months ago in Jira 0 Planning to implement

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

JIRA integration needed at the portfolio and product family levels.

We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
Wen-Wen Lin about 4 years ago in Jira 2 Future consideration

Inform user if Version export to Jira fails due to existing fix version in Jira

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
Guest 4 months ago in Jira 0 Future consideration

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 over 2 years ago in Jira 0 Future consideration