Warn when there are incomplete Jira webhook settings
When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
Madeleine Black
over 1 year ago
in Jira
0
Future consideration
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner
3 months ago
in Jira
0
Future consideration
When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...
Guest
almost 8 years ago
in Jira
5
Future consideration
Allow integrations such as Jira at the Product Line level
Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Steve C
almost 2 years ago
in Jira
0
Future consideration
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The i...
Matt Case
almost 8 years ago
in Jira
13
Future consideration
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA.
Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer
over 8 years ago
in Jira
15
Future consideration
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, mast...
Guest
about 5 years ago
in Jira
5
Future consideration
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush
9 months ago
in Jira
0
Future consideration