Jira
Sort by:
Trending
Filter by:
Status
Showing 263 of 9056
3
VOTE
Need easier way to link to existing Jira records!
Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
0
Future consideration
6
VOTE
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
1
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
1
VOTE
Jira Integrations: Map Aha Releases to a custom Jira Version Field
Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...
0
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
10
VOTE
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
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
4
VOTE
Ability to apply a Jira Integration Template to an EXISTING Jira Integration but only have it update the URL and Jira Login/Password settings
We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I ...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved