Jira
Sort by:
Trending
Status:
Future consideration
Showing 104
35
VOTE
Jira Integration of custom calculated field
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release ...
0
Future consideration
46
VOTE
JIRA Integration: Adding Master Feature, Initiative & Goal Record Links
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
2
Future consideration
44
VOTE
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...
9
Future consideration
32
VOTE
Honor Changing Jira Issue Types
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 it...
7
Future consideration
11
VOTE
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 possi...
0
Future consideration
26
VOTE
Add support for Jira "Parent Link" field
Jira Portfolio adds the Parent Link custom field to Jira. Aha! should support mapping this custom field so that the link between a feature and an initiative in Aha! can be reflected into Jira.This field has the custom field type of "com.atlassian....
6
Future consideration
62
VOTE
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...
16
Future consideration
55
VOTE
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 ...
13
Future consideration
11
VOTE
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite ...
2
Future consideration
20
VOTE
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, master ...
3
Future consideration