Jira
Sort by:
Trending
Status:
Showing 270
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
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
1
VOTE
The ability to create a report to show if there are any pending Integration Updates rather than having to manually look for them
Simplify the ability to know if there are pending updates to either Import or Ignore by running/scheduling a report with this data by Workspace and Integration, etc.
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
1
VOTE
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
1
VOTE
Calculate Epic Completion Based on JIRA Epic Completion
The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
0
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
Filter which JIRA issues get reflected back to Aha!
Aha! allows product managers to stay at the 40k foot level, while JIRA is used by our development team, which means it contains lots of small implementation details. If all the bugs and tasks being logged by my developers in JIRA reflect back into...
4
Already exists
© 2025 Aha! Labs Inc.•All rights reserved