ADD A NEW IDEA

Jira

Showing 84

Re-enable conversion of Features to Requirements when JIRA integration is active

In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
Mike Ward almost 8 years ago in Jira 4 Shipped

Allow features to be linked to existing JIRA issues

If we already have issues in JIRA that are duplicates of features in Aha! we want to be able to manually create a link between them.
Chris Waters over 9 years ago in Jira 9 Shipped

Map Aha Initiative to JIRA Portfolio Initiative

JIRA Portfolio allows for the notion of Initiatives. Portfolio is good for provide views for about 3 months (short-term), beyond that we have found it to struggle. It will be good to sync initiatives so it is possible for engineering to see what i...
Project Parker over 6 years ago in Jira 11 Shipped

Support the "links to" field mapping with next-gen templates in Jira

My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates. Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" ...
Guest over 5 years ago in Jira 12 Shipped

Support for "Select list (cascading)" field type in JIRA

JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...
Guest over 6 years ago in Jira 10 Shipped

Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.

Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
Guest over 6 years ago in Jira 7 Shipped

Add a tag to requirements, and sync it with jira labels

Why is it useful? Our Product team uses tags in Aha and labels in jira to help in planning which team works on which requirement / user story, to make sure that one team working in the release is not over-burdened. Sometimes one team works on a...
Guest about 9 years ago in Jira 2 Shipped

JIRA Statuses for Features and Requirements

We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...
Guest over 8 years ago in Jira 6 Shipped

Custom Field two-way sync for JIRA

I would like the ability to make custom fields 2way synchronized in JIRA. Currently they sync from Aha! to JIRA, but not back from JIRA to Aha!
Melissa Hopkins about 9 years ago in Jira 2 Shipped

JIRA Import multiple issue types as requirements mapped to parent feature

As a PO, I’d like to import multiple issue types (i.e. bug, story) as requirements that map to their parent features so that existing Jira Projects can be imported into Aha! Products in a single import
Danny Archer about 9 years ago in Jira 4 Shipped