Jira
Sort by:
Trending
Status:
Future consideration
Showing 270
21
VOTE
Support mapping JIRA Tempo Account field
When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
8
Unlikely to implement
17
VOTE
3
VOTE
Excel Documents Not Sending to Jira Custom fields
Who would benefit? What impact would it make? Less back and forth with BA and Developers to correct transfer error How should it work? Underneath our field "Functional Requirements" in the attch items, when I attach an excel document it does not t...
0
Future consideration
5
VOTE
22
VOTE
Have users in Jira and Aha matched for comments, updates etc
I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there.
Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
1
Unlikely to implement
2
VOTE
Automatically push Epics/Features in Aha! to JIRA
What is the challenge? As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I ...
0
Future consideration
14
VOTE
Automatically send feature(s) to integrated system
As a product manager I want to have a feature I just created be automatically created in my integrated system, such as Jira.
Adding a check box in the integration configuration for "Automatically send issue to integrated system" would be an easy w...
5
Unlikely to implement
13
VOTE
Auto Resend all Fields per release
Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
2
Future consideration
3
VOTE
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...
0
Future consideration
18
VOTE
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
11
Already exists
© 2025 Aha! Labs Inc.•All rights reserved