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 (...
Guest
about 5 years ago
in Jira
1
Future consideration
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...
Guest
almost 8 years ago
in Jira
2
Unlikely to implement
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...
Max Cascone
about 7 years ago
in Jira
3
Already exists
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...
Kyle Shannon
11 months ago
in Jira
0
Future consideration
Allow users to refresh all Aha! features from a linked JIRA integration.
Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow
about 9 years ago
in Jira
0
Already exists
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...
Guest
almost 5 years ago
in Jira
1
Future consideration
Would like to track when a feature was sent to JIRA and by who? Can you please let me know how I can accomplish this?
JIRA_KEY (I am able to pull)
JIRA_KEY_CREATE_DATE (Not known)
JIRA_KEY_CREATED_BY
Thank you
//Need this for SOC compliance//
Sasi Ravichandar
about 5 years ago
in Jira
0
Future consideration
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...
Wen-Wen Lin
about 5 years ago
in Jira
1
Future consideration
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 ...
Leanne Miller
about 4 years ago
in Jira
0
Future consideration