ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 103

Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. It would be great to also access the Resolution status from Jira to handle this c...
Guest about 5 years ago in Jira 16 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The ...
Matt Case over 4 years ago in Jira 13 Future consideration

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer about 5 years ago in Jira 12 Future consideration

JIRA Integration: Adding Master Feature, Initiative & Goal Record Links

The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
Project Parker over 2 years ago in Jira 2 Future consideration

Include comments when importing from Jira

When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Ji...
Guest over 4 years ago in Jira 3 Future consideration

Jira Integration of custom calculated field

We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release ...
Russell Roach 3 months ago in Jira 0 Future consideration

JIRA: Detect default unit of time tracking

Aha! relies on time tracking in JIRA being set to the default value of minutes. If the value in JIRA has been altered to anything else, it throws time tracking estimates off. As of the 6.4.x version of the JIRA REST API a GET is available that ret...
Danny Archer about 5 years ago in Jira 7 Future consideration

Honor Changing Jira Issue Types

Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item. Example: Support reports a "Support Defect", Dev reviews, changes it...
Kathy Landon about 2 years ago in Jira 7 Future consideration

Run As User JIRA Webhook Integration Account should not consume a license seat

https://support.aha.io/hc/en-us/articles/115005972743?input_string=jira+webhook+run+as+user+is+defaulting+to+me%2C+and+it+looks+like+i%27m+synchronizing+all+work+to+jira tells us that if we don't want all imported changes from JIRA to Aha to appea...
Jared Morgan almost 3 years ago in Jira 7 Future consideration

Map Aha Initiative to JIRA Portfolio Initiative

JIRA Portfolio allows for the notion of Initiatives. Portfolio is good for provide views for about 3 months (short-term), beyond that we have found it to struggle. It will be good to sync initiatives so it is possible for engineering to see what i...
Project Parker about 3 years ago in Jira 4 Future consideration