Jira
Sort by:
Trending
Filter by:
Status
Showing 243 of 8288
12
VOTE
Improve visibility of integrations update modal
When users set up an integration and select "auto import records", they are not immediately aware that some records will not just automatically import into Aha! (i.e. those that don't have a parent record that is sync'd). These users are not able ...
0
Likely to implement
6
VOTE
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
0
Future consideration
2
VOTE
Add better error handling for 'unhandled error exceptions'
When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
0
Future consideration
74
VOTE
Include comments when importing from Jira
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...
5
Future consideration
11
VOTE
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...
1
Future consideration
3
VOTE
34
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 poss...
1
Future consideration
66
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 i...
13
Future consideration
49
VOTE
20
VOTE
