Jira
Sort by:
Popular
Status:
Showing 231
2
VOTE
JIRA integration to track correct users in history of issues
Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
1
Future consideration
2
VOTE
2
VOTE
Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status
We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
1
Future consideration
2
VOTE
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
3
Already exists
2
VOTE
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
0
Future consideration
2
VOTE
Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
0
Future consideration
2
VOTE
When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration
I have a JIRA 2.0 Integration with Aha! Features mapped to Epics in JIRA. I set the directionality of the name and description fields to be one way from Aha! to JIRA. Other fields can be mapped as required. When I perform an import from developmen...
2
Future consideration
2
VOTE
Synchronising JIRA backlog with Aha ordering
Currently I use the feature board loads - organise all my features into releases with certain priorities and I use capacity planning and it's great. And I have a JIRA integration so anything I create in Aha is pushed out to JIRA with the correct r...
1
Future consideration
2
VOTE
Sync with Jira include ability to link back to Aha Item
When configuring sync between Aha and Jira, it should include the ability to have a URL back to the associated Aha idea inserted in Jira field. This would allow Product and Engineering a better way to trace stories back to the original Features, O...
1
Future consideration
2
VOTE
Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release
Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
0
Future consideration