Jira
Sort by:
Trending
Filter by:
Status
Showing 210 of 7159
1
VOTE
44
VOTE
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 i...
9
Future consideration
74
VOTE
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...
17
Future consideration
7
VOTE
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
0
Future consideration
60
VOTE
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 i...
13
Future consideration
2
VOTE
Ability to use "belongs to" relationship in Aha to map to "is contained by" link type in Jira
I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...
1
Already exists
22
VOTE
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
1
Future consideration
2
VOTE
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...
2
Future consideration
54
VOTE
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 Jir...
5
Future consideration
28
VOTE
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, mast...
3
Future consideration