Jira
Sort by:
Recent
Status:
Showing 264
9
VOTE
Include JIRA records in linked records
We want to show a dependency of one of our Features on a deliverable from another team without having to create a separate feature and map and sync it through the regular JIRA integration. I think being able to import the JIRA link (and descriptio...
2
Unlikely to implement
4
VOTE
3
VOTE
Show JIRA import progress in numbers
As a power user, I want the progress to print to the screen in numerals (e.g. "1 of 250 features imported") so that the information prevents me from re-attempting an import. My current workaround: navigate to the Features -> Board and check the...
0
Unlikely to implement
2
VOTE
Keep unsupported 3rd party Jira tag as it is upon syncing
In Jira, it is possible to render Gherkin by using 3rd party plugin.
After modify the description field in Aha! and synced with Jira, the format is ruined by Aha!.
Original Description on Jira:{code:gherkin} Scenario: The empty state text shows...
0
Will not implement
13
VOTE
2
VOTE
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...
0
Already exists
5
VOTE
Allow "Predefined choice list" to select multiple items
Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
0
Unlikely to implement
1
VOTE
Provide the ability to map multiple ticket types to requirements
We are hooking Features into Epics, and discussing with development and the rest of the product team, the individual enhancements, new features, and tasks that are required to be performed for the "Epic" to be completed. Aha/Jira integration only ...
3
Already exists
11
VOTE
Sync story points to Jira without Capacity Planning
My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira.
Currently this is only accomplishable when you have enabled capacity planning, which causes me...
1
Future consideration
18
VOTE
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
11
Already exists
© 2025 Aha! Labs Inc.•All rights reserved