Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 271 of 9563

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Guest over 9 years ago in Jira 11 Already exists

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner over 1 year ago in Jira 0 Future consideration

Support mapping tags to JIRA multicheckboxes

Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
Austin Merritt over 6 years ago in Jira 0 Future consideration

Including Dependencies in Jira integration at requirements/story level

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Guest over 3 years ago in Jira 0 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 7 years ago in Jira 0 Future consideration

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest about 10 years ago in Jira 9 Unlikely to implement

Map Created By User from Jira

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Guest over 2 years ago in Jira 1 Already exists

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Guest over 5 years ago in Account settings / Jira 1 Future consideration

Convert story to epic in Jira when promoting requirement to feature

In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
Guest about 10 years ago in Jira 2 Unlikely to implement

Allow editing to wiki-rendered fields in Jira

Who would benefit? Jira integration users What impact would it make? Currently Jira is sending broken formatting when fields leverage wiki-rendering with tables How should it work? If a user makes an edit to a table in Jira on a wiki-rendered fiel...
Stephanie Lechner over 1 year ago in Jira 1 Future consideration