ADD A NEW IDEA

Jira

Showing 171

Jira sprint dates as feature end dates

With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
John Biltcliffe about 5 years ago in Jira 4 Future consideration

Sync initial estimate field in integrations

I am able to sync my detailed estimate field in Jira integrations, but not initial estimate.
Alina Mavis over 1 year ago in Jira 5 Future consideration

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest about 9 years ago in Jira 9 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 3 years ago in Jira 0 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 t...
David Vins over 5 years ago in Jira 8 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 6 years ago in Jira 5 Future consideration

Convert story to epic in Jira when promoting requirement to feature

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest about 9 years ago in Jira 2 Future consideration

Warn when there are incomplete Jira webhook settings

When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
Madeleine Black almost 2 years ago in Jira 0 Future consideration

Map to a persona name value in integrations

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

Manual Sending of Requirements to integrated development tool

Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R about 1 year ago in Jira 2 Future consideration