ADD A NEW IDEA

Jira

Showing 245 of 8636

The Aha <->Jira Integration Mappings should be Transparent to User

Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Guest about 2 years ago in Jira 1 Already exists

Enable external link handling for Jira and other integrations

Jira has a native link handling functionality that displays links in-line on issues. To recreate the same behavior, I have to create a custom field for the link to target (meaning I end up with a bunch of extra fields) and need to reciprocate acro...
Yancey Larochelle-Williams about 2 years ago in Jira 0 Future consideration

Jira integration needs to include Tempo Team field

This is a blocker for us.
Tracey locke about 2 years ago in Jira 1 Future consideration

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.
David Strathy-Miller about 2 years ago in Jira 0 Future consideration

Including Dependencies in Jira integration at requirements/story level

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S over 2 years ago in Jira 0 Future consideration

Resolve links - Aha-JIRA integration

Wish links are resolved to the respective JIRA Tickets. Not everyone (non-Product Team) has access to Aha :(
Guest over 2 years ago in Jira 0 Future consideration

Ability to map Jira Web Links with Aha! URL at Integration

Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
Tej Namala over 2 years ago in Jira 0 Future consideration

JIRA integration to track correct users in history of issues

Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
Austin Churchill over 2 years ago in Jira 1 Future consideration

Synchornize workflow approvals from Aha! to Jira

Allow for mapping Aha! approvals to Jira via the integration. When a team member moves an item in Jira to a status that requires an approval in Aha!, pass the approval status back to Jira once it is updated in Aha!
Guest over 2 years ago in Jira 2 Future consideration

Many to one mapping for field integrations

The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
Jerimiah Rudden over 2 years ago in Jira 0 Future consideration