When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black
6 months ago
in Jira
1
Future consideration
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black
6 months ago
in Jira
0
Future consideration
Run As User JIRA Webhook Integration Account should not consume a license seat
https://support.aha.io/hc/en-us/articles/115005972743?input_string=jira+webhook+run+as+user+is+defaulting+to+me%2C+and+it+looks+like+i%27m+synchronizing+all+work+to+jira tells us that if we don't want all imported changes from JIRA to Aha to appea...
Guest
about 5 years ago
in Jira
17
Future consideration
When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
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
Guest
11 months ago
in Jira
0
Future consideration
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
Reut Levi
7 months ago
in Jira
1
Future consideration
Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes i...
Kathy Landon
over 4 years ago
in Jira
10
Future consideration
Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status
When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow.
It would be great to also access the Resolution status from Jira to handle this c...
Guest
over 7 years ago
in Jira
17
Future consideration
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 7 years ago
in Jira
13
Future consideration