Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 265

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

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

Set Dates of Feature Based on Status in JIRA

I'd like to see the Aha!/JIRA integration be updated to have an option to set dates of features (and possibly other items) based on Status that is in JIRA. Example: I create a Feature in Aha! and integrate/export to JIRA When Feature (referred t...
Aaron Kremin almost 7 years ago in Jira 0 Unlikely to implement

Allow Jira Integration to synchronize External Release Dates

In Jira, we track external Release Dates. Aha does not allow external release dates to be synced. This means our Jira is reporting inaccurate information.
Guest over 1 year ago in Jira 0 Future consideration

Jira integration needs to include Tempo Team field

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

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

Inform user if Version export to Jira fails due to existing fix version in Jira

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
Guest over 1 year ago in Jira 0 Future consideration

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

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 about 6 years ago in Jira 1 Already exists

Feature History - Should show when a JIRA integration Link is Deleted

It would be valuable for the Features -> History audit trail to include information for when a JIRA integration link is deleted.
Matt Case over 7 years ago in Jira 0 Future consideration