With the Jira integration it is possible to pull through the Sprint name as a custom field into Aha Master Features/Features. It would be useful to be pull through the sprint finish date and apply that to all linked items within Aha. This would al...
John Biltcliffe
over 6 years ago
in Jira
5
Future consideration
HYCU is a cloud based modern data protection, backup and recovery for SAAS applications. This integration reduces down time by recovering data lost via a ransom attack or human error. Every company should have a backup and recovery plan. We make i...
Guest
over 2 years ago
in Integrations
0
Future consideration
Ability to create a report of integration errors across multiple workspaces
Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko
over 4 years ago
in Jira
7
Likely to implement
Ability to send Aha Defects to Rally as Rally (CA Agile) Defects
We need the ability to send defects to Rally. Currently, we are only able to send features/ user stories which cannot be converted to defects once they are in Rally.
Guest
about 8 years ago
in Rally
2
Future consideration
Change revision history descriptors for text field updates
It seems that some fields when updated via integration show a descriptor as XYZ changed integration link for Capability..123". This can be found in some values fields. Other fields like description simply state " XYZ updated the capability 123". T...
Karla Johnson
about 3 years ago
in Rally
1
Future consideration
Improving handling when Jira users change issue type across record hierarchy
Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
Stephanie Lechner
about 2 years ago
in Jira
0
Future consideration
Bi-directional support for Area Level fields in ADO integration
What is the challenge? Currently we offer Area Level fields in our ADO integration for each Area Level. This allows us to receive the unique Area Level from ADO, but currently updates in Aha! do not change the Area Level back in ADO despite the se...
Custom field added to Integration import notification window
What is the challenge?
I have to sift line by line through integrations in order to import only what I want and ignore what I don't want
What is the impact?
time=consuming with a large volume of features
Describe your idea
Allow me t...
Julianne Dunnuck
3 months ago
in Integrations
0
Future consideration
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
Danny Archer
almost 8 years ago
in Dependencies / Jira
3
Future consideration