Jira
Sort by:
Trending
Status:
Showing 260
3
VOTE
Merge Custom Fields into One Field when they are carried over from Idea to Feature
At idea stage you capture information about the idea in multiple fields, when you promote this to a feature if this information was merged into one 'Body' field, then I would save time not having to copy and paste those fields into one field.
Ha...
0
Unlikely to implement
3
VOTE
Feature Email update notification to include link direct to Jira record
From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
0
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
3
VOTE
Update Jira integration when Jira custom fields were added
It looks like if you add a custom field in JIRA, Aha will not recognize it unless you delete the integration and add a new one, which means you need to relink everything.
You should be able to go through the integration UI and add new field mappi...
1
Already exists
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
4
VOTE
JIRA integration without admin account rights
At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
0
Already exists
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...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved