Jira

We use Master Releases when we have multiple products shipping together. I need the Master Release name to appear in Jira for reporting. I'm flexible as to how this can be done. Maybe a way to create a custom field on the feature level that auto-p...

Some users may not want versions created in JIRA for each release in Aha! Add an option to the JIRA integration configuration to disable the creation and linking of releases to versions.

What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...

When configuring a webook in Jira, there is a checkbox: ☐ "Exclude body" Request with empty body will be sent to the URL. Leave unchecked if you want to receive JSON. If someone accidentally checks that, Aha! won't get any updates. There is no log...

Now that Atlassian has announced that Jira Server will not be supported by 2024, we need to find a way to migrate the existing Aha! - Jira Server integration without having to re-establish the connection. The recommended methods indicated in the l...

I have JIRA linked with Aha! and can see the JIRA Id and key - which is great. But I would love to have the URL link available in my list report as well. It looks like there is a field JIRA URL, but it is blank. What is it used for?

We map Aha! features to epics in Jira, with Aha! requirements as stories. When an epic already exist in Jira with child stories, I want to link that epic to a feature in Aha! and have the child stories immediately sync over as requirements.

One of the fields we have in JIRA has over 100 values. Mapping each value to Aha is a no go. The interface to manually drag and drop each value to the correctly mapped value is slow, cumbersome and took over 60 seconds to just do 1. It will be pr...

This would be very helpful since without it Product Manager doesn't get to know if Dev team has added any new stories during grooming. Currently such stories although result in creating features, they are only visible on Feature Board view under r...

Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...