Jira
Sort by:
Trending
Filter by:
Status
Showing 240 of 8115
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
4
VOTE
Jira Sync Aha Release Phases and To-Dos
Please enable the ability to sync a release phase to an Epic in Jira. And also sync release phase To-Dos to tasks in Jira. Use Case: I have a release template with my release phase and associated to-dos. These to-dos are what govern my Jira tasks....
0
Future consideration
2
VOTE
Make JIRA webhooks URL specific
Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
0
Future consideration
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
5
VOTE
Set Rank order from Jira to Aha!
When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...
1
Future consideration
8
VOTE
Map Aha! products to Jira components
Allow the mapping of Products in Aha! to Component/s in Jira.
In order to automatically assign Aha! items pushed over to Jira to the right component, I've had to create a custom field in aha! with a pick-list of the component names from Jira. I c...
3
Already exists
5
VOTE
5
VOTE
We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.
We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...
1
Future consideration
10
VOTE
2
VOTE
