Share your product feedback

ADD A NEW IDEA

Jira

Showing 263

Automatically create/update Notification Groups based on location hierarchy

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...
Guest over 2 years ago in Jira 0 Future consideration

Add more filters to integrations import

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer about 1 year ago in Jira 0 Already exists

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 over 9 years ago in Jira 2 Unlikely to implement

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 almost 5 years ago in Account settings / Jira 1 Future consideration

Allow for Delete of Jira Issue

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.
Kenny Burnham over 5 years ago in Jira 2 Unlikely to implement

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

Allow requirements to be associated with the release record

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
Guest about 5 years ago in Jira 0 Future consideration

Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories

I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!. We'd much prefer that this not be the ca...
Doug Wilson almost 5 years ago in Jira 1 Future consideration

Ability to Integrate Ideas with Jira Service Desk

What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
Matt L 7 months ago in Jira 0 Future consideration

The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.

Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
Andrew Sweet over 5 years ago in Jira 1 Future consideration
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved