Skip to Main Content
ADD A NEW IDEA

Jira

Showing 171

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest about 7 years ago in Jira 3 Future consideration

Product Line initiatives linked back to Jira Epic

We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis over 4 years ago in Jira 1 Future consideration

JIRA integration needed at the portfolio and product family levels.

We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
Wen-Wen Lin about 5 years ago in Jira 2 Future consideration

Support bulk remove of JIRA links from "Features List"

Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest about 8 years ago in Jira 1 Future consideration

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! upda...
Guest over 8 years ago in Jira 2 Future consideration

Auto Resend all Fields per release

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
Guest over 5 years ago in Jira 2 Future consideration

Map one Aha release to several Jira projects

We have several Jira projects aiming towards the same release. When importing fixVersions from several Jira project to one product in Aha we get one release for each project/integration in Aha. This means that if we have 10 projects aiming for the...
Guest almost 6 years ago in Jira 0 Future consideration

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black almost 2 years ago in Jira 1 Future consideration

Show custom field names on integration errors

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley about 3 years ago in Jira 1 Future consideration

Support updating JIRA Integration Links by csv upload

While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
Garret Duffy about 1 year ago in Jira 0 Future consideration