In GitHub integration, we would like to map a custom field called "Repository" to a static value that is identical for all issues from the one GitHub integration. That way we could then show the value as a label and also filter by it in feature vi...
Guest
over 3 years ago
in GitHub
0
Future consideration
Select workspaces that ideas can be created/searched through Zendesk integration
We'd like a similar feature to the Salesforce integration where we can choose which workspaces ideas are added and searchable in the Zendesk integration. For a variety of reasons, we have ideas in several workspaces, but we only want ideas to crea...
Steven Chan
over 3 years ago
in Integrations
0
Future consideration
It would be great if the "to-do's" in AHA Requirements, can be mapped to Rally as "to-do's" in the users stories. And, update both ways if marked as completed. Here is a similar idea for Azure DevOps; it would be great to see this for Rally as wel...
Guest
over 3 years ago
in Rally
0
Future consideration
Allow 2-way integration to Jira FixVersion/s field from text field
Instead of having to integrate Aha! Release to Jira FixVersion/s, let Aha! text fields specify the name of a version and have it update the FixVersion in Jira based on a matched name. If no matched name exists, then throw an integration error just...
Jor Bratko
over 3 years ago
in Jira
0
Future consideration
Pivotal Stories added to Epics converted to Requirements in Features
The Pivotal integration is good, but fails to capture a common case for us. Our teams often add new Stories to Epics that are essentially Requirements on the corresponding Feature. We track progress through these Stories/Requirements. Right now, t...
Christopher M
over 3 years ago
in Pivotal Tracker
0
Future consideration
We use integrations to calculate the 'Feature % Complete' which updates the ‘Progress Bar’ automatically but we have to select the progress to be set to 'Manual'. We want to update the visualize progress on a roadmap selections by adding the ‘Prog...
Mike Jacobson
over 3 years ago
in Rally
0
Future consideration
Support iovation LaunchKey for Multi-Factor Authentication
Currently you seem to only support stronger authentication options for those customers who use Duo (under their own contract). While we would be OK with an Aha! contracted strong authenticator, if we must supply our own then our preference would b...
Guest
over 7 years ago
in Integrations
0
Unlikely to implement
Display the Name of the Ticket a Feature Is integrated with as column option
When creating a feature list there needs to be the option to show a column that displays the the actual ticket the feature is integrated with. Right now I can get the name of the integration but I want to see the specific ticket name and number in...
Gary David
almost 4 years ago
in Integrations
1
Already exists
In some cases depending on workflow stories created in JIRA prior to an Epic being linked in Aha do not flow to the aha record. In this case we would like to have an option to not only resend the epic record values but also all the linked records.
David G
almost 4 years ago
in Jira
0
Future consideration
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
Guest
over 7 years ago
in Jira
0
Unlikely to implement