Integrations
Sort by:
Trending
Filter by:
Status
Showing 916 of 8637
1
VOTE
Show Integration Errors Next To Integration Link
So often tickets stop syncing between JIRA & Aha! for one reason or another and yes, I understand there is an Integration Updates modal, but when you are working in a ticket, I should get a little error icon next to the link, in the record, if...
0
Future consideration
2
VOTE
Allow creation of idea at Salesforce Account level
Right now, you can link an already created idea at the Salesforce account level, but you can create a new idea. This has been requested from many of our solution architects supporting current customers. Would be a big help in encouraging additiona...
1
Already exists
2
VOTE
2
VOTE
Add prefixes to feature stories in Rally
When integrating with Rally using the "Feature -> User Story, Requirement -> User Story" mapping, it would be great if we could give custom prefixes to the feature stories names in Rally without having those prefixes displayed in Aha.
We us...
0
Unlikely to implement
1
VOTE
Ability to execute a AzureDevOps query and display results in charts on Aha Dashboard
For the teams who uses AzureDevOps as ALM tool , It would be great flexibility to view a snapshot of the query results on the Aha dashboard. It does not need to be sync but can be pulled async.
0
Future consideration
1
VOTE
Allow TFS integration to map bidirectionally for fields that are not in a built-in System.State.
Currently, the TFS integration does not support mapping arbitrary string fields to the Aha! workflow status field in a bi-directional way. Only the built-in System.State field in TFS can be mapped bidirectionally.
2
Future consideration
2
VOTE
Sending Feature to Pivotal Tracker should send story point Estimate
When Story Points are added to a story in PT, they are updated in Aha. This is great.
However, it would also be nice if the Feature estimate in Aha (if specified in Story Points) was also sent to PT when the feature is pushed using the Action -&g...
0
Already exists
1
VOTE
2
VOTE
1
VOTE
Release Should Be Marked as Shipped only when all Integrations for JIRA projects are shipped
If multiple integrations are enabled at release level, allow workflow rule for release to be considered as shipped when all integrated JIRA projects have shipped the release If someone marks the release as shipped in JIRA, its changing the status ...
0
Unlikely to implement