ADD A NEW IDEA

Jira

Showing 261

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

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 over 5 years 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). Unless...
Guest almost 6 years ago in Jira 0 Future consideration

Allow Mapping of Requirement Type from Jira to Aha!

Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...
I R over 1 year 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

Provide applicable error message when a Jira integration can't authenticate due to a captcha challenge issue

When attempting to set up a Jira integration, authentication can fail with a 403: CAPTCHA_CHALLENGE error we can see in the logs, but there is no applicable message on the integration-set up screen. It just says "We could not connect to your Jira ...
Emily Yankush over 1 year ago in Jira 0 Future consideration

The ability to create a report to show if there are any pending Integration Updates rather than having to manually look for them

Simplify the ability to know if there are pending updates to either Import or Ignore by running/scheduling a report with this data by Workspace and Integration, etc.
Eric Hutchins over 1 year ago in Jira 0 Future consideration

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

Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt

We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
Guest almost 5 years ago in Jira 0 Future consideration