In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
Karie Kelly
almost 3 years ago
in Integrations
0
Future consideration
Including Attachments from Comments for Jira Integration
It would be useful if we had the ability to push attachments made on comments, to Jira. Today, only direct attachments (to features or requirements) are supported, but from a UX perspective, attachment from comments should be included too, OR an a...
Reut Levi
almost 5 years ago
in Integrations
4
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
over 7 years ago
in Dependencies / Jira
3
Future consideration
Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox
about 4 years ago
in Jira
0
Future consideration
Dependency Relationship Removed does not Update Aha or vice versa
What is the challenge? If a dependency relationship is removed in Azure DevOps, it does not remove it in Aha. If a dependency relationship is removed in Aha, it does not remove it in Azure DevOps. What is the impact? Have to go to both systems to ...
Guest
3 months ago
in Integrations
0
Future consideration
Allow a single Azure DevOps webhook to support updates across multiple Aha! integrations
With Jira, a single Aha! webhook added at the system level supports updates across all Aha! integrations.
This makes scaling integrations simple as after the first setup, a user never has to add another webhook.
With Azure DevOps (TFS), each i...
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black
over 2 years ago
in Jira
1
Future consideration
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Reload configuration for all child integrations when a template integration mapping is updated
If you have an integration template with mappings that are inherited by child integrations, you can adjust the mapping step on that integration template to propagate your new mapping to all the integrations using that template. If you are doing so...
Maria Plotkina
8 months ago
in Integrations
0
Future consideration