Would be great to be able to map Aha! status to GitHub labels. We use labels in Git to mark phase of the issue, because there are only 2 statuses in Git (Open, Close). This way we have more clear overview on the progress, and it would be great if ...
It would be great to be able to easily communicate the rank order of a feature from Aha! to JIRA. If we created a custom field in JIRA for "Aha! Rank" and send the rank over to that field that would be a step in the right direction. Or alternately...
Ability to associate a feature created in JIRA to a Master feature in Aha!
We have Engineers that take the Customer focused epic and break that down into multiple epics (sometimes technical), so we don't want to have them to get out of the tool they work in (JIRA) and switch to Aha!, just to enter the new features for th...
Our Marketing team uses HubSpot to schedule social media posts, for example. It would be awesome to plug into their tool so we can push marketing tasks with relative dates, and they can relay when those are ready and completed. It's unlikely marke...
Allow customization of on-prem Jira link displayed in Feature details so that link actually works
High-level:
The URL that is used for integration with our on-prem Jira implementation is not the same as the URL that we use while on our network. Consequently, clickin on the Jira link within any feature takes us to nowhere. This enhancement req...
An Aha feature pushed to Rally creates the Feature/User Story in Rally as well as the Release information. An Aha feature in the Parking Lot (not tied to a specific release) will still be created in Rally, but there is an error message with the re...
Allow use of a template to create integrations through REST API
In order to integrate on features from Aha to Rally, we have to create 1000+ iterations from products in Aha to project teams in Rally. We found that we can create integrations via the API, but would like to base these on a template as we want to ...
Elaine Edwards
over 4 years ago
in Integrations
0
Shipped
The Blocked field is an important status identifier in the CA/Rally process that acts like a toggle rather than a defined status value. It would be helpful to understand and be able to convey this blocked state to the product owner in Aha!
Automated Integration Migration for Aha! - Jira Server to Jira Cloud
Now that Atlassian has announced that Jira Server will not be supported by 2024, we need to find a way to migrate the existing Aha! - Jira Server integration without having to re-establish the connection. The recommended methods indicated in the l...
We currently use Google SSO for our JIRA system. The Aha! integration however requires a username/password user account & not an SSO user.
I need to be able to use an SSO user for the integration, since that is the only option that our JIRA ...