Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 212 of 7279

Need an option to sync Jira fixVersion "Name" instead of "ID"

Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
Guest about 6 years ago in Jira 0 Already exists

Update the JIRA sprint field with better import

Currently if a story has belonged to more than one sprint, the sprint field concatenates the sprint. For example, a story was in sprint 2019.5 and then moved to 2019.16 and then moved to unscheduled. In JIRA the story is none +2 indicating tha...
Guest about 3 years ago in Jira 3 Already exists

After Importing Feature from Jira, show reference # id(s) for imported item(s).

Today, after importing a Jira item into our Feature list, the import completion screen just indicates the number of features imported. I'd like to be able to go directly to that imported item so that I can make some changes to it, but instead I ha...
Zayna Schaffer about 3 years ago in Jira 0 Future consideration

Link to Multiple JIRA Items

On some occasions we will end up with multiple JIRA tickets for the same item in AHA. We'd like to be able to track each of these in Aha, but most importantly be able to pull the time tracking data into aha across all of the tickets.
Guest over 6 years ago in Jira 2 Unlikely to implement

Sync @ Mentions With Linked JIRA Users

Useful to keep users of JIRA and Aha in sync between systems without managing Watchers across installations. I've noticed that @ mentions in Aha! do not match the JIRA username on comments. I want to ensure that JIRA users are notified when I @ m...
Ryan Schultz over 6 years ago in Jira 0 Unlikely to implement

Integration with Jira: Ability to filter imported Jira releases/versions by date

Integration with Jira: Ability to filter imported Jira releases/versions by date Problem: A lot of manual clean up is required when integrating with Jira projects that have many past releases. There is no functionality to filter out old releases....
Guest over 3 years ago in Jira 0 Already exists

Allow for "approve incoming changes" in Jira integration

There is currently an option to approve outgoing changes or incoming records, but not incoming changes. The current options are: - Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to...
Guest over 3 years ago in Jira 0 Future consideration

JIRA integration: support mapping of “Release name” into custom field

Mapping of “Release name” towards custom fields in JIRA integration instead of “fixed version” or “affected version” only currently the AHA-Jira integration only allows a mapping of "release name" values in either "fix version" or "affects versi...
Florian Kette almost 4 years ago in Jira 1 Unlikely to implement

JIRA Tree CustomField

Support in the v2 JIRA API for JIRA field types of Tree CustomField (multiple choices).
Guest almost 4 years ago in Jira 0 Future consideration

Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query

Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc. Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha. Requirement: The query should bring...
Guest about 4 years ago in Jira 0 Unlikely to implement