Jira

Showing 262

Assign Integration to Specific User

Need the ability to assign a JIRA integration to a specific Aha! user instead of having each PM need to navigate to the integration and select Run As.

Yancey Larochelle-Williams over 4 years ago in Jira 0 Future consideration

1 VOTE

Add option to show additional columns/fields in "Integration updates" window for Jira

The "Integration updates" window currently only shows the issue summary of incoming issues. Presumably the JSON payload being received by Aha contains the full set of information for the incoming issue ... it would be incredibly valuable to be abl...

Gene Lewin over 1 year ago in Jira 0 Future consideration

1 VOTE

Please make the Jira Integration Ticket Link clickable

Please make the Jira Integration Ticket Link clickable, so it launches Jira

Guest over 1 year ago in Jira 1 Already exists

4 VOTE

For Jira integration, enable ability to prevent releases being automatically created in Jira (and/or enable this for releases in parking lot)

Right now we have an integration set up between Jira and Aha (which is extremely useful). However, whenever a feature in Aha that's linked to an issue in Jira has its release updated (e.g. moved from "v1.12.0" to "Backlog"), if the release to whic...

Guest about 6 years ago in Jira 0 Future consideration

2 VOTE

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 3 years ago in Jira 0 Future consideration

1 VOTE

JIRA Integration - Hide 'Send To' Options

Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).

Kyle Kinder over 1 year ago in Jira 1 Future consideration

4 VOTE

Broken Atlassian Webhook

Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date). U...

Guest over 6 years ago in Jira 0 Future consideration

2 VOTE

Jira integration needs to include Tempo Team field

This is a blocker for us.

Tracey locke about 3 years ago in Jira 1 Future consideration

4 VOTE

Allow parking lot features and releases to not be sent to Jira

I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...

Kyle Cain over 6 years ago in Jira 1 Already exists

3 VOTE

Make fixed workflow transition enforcement optional for Jira integratations

Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it. With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...

Daniel Hirschberg about 5 years ago in Jira 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY