Skip to Main Content
ADD A NEW IDEA

My ideas: Jira

Showing 87

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 over 9 years ago in Jira 4 Shipped

Need to "Link with existing issue in JIRA" at requirement level

We have JIRA and Aha today and the tools are integrated as follows: Aha feature - JIRA Epic Aha requirement - JIRA story NA - JIRA sub-task For some reasons, I had to delete the integration with JIRA for a specific product line...
Emilie Takeda almost 9 years ago in Jira 7 Shipped

Sync "Sprint" Field from JIRA

Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...
Guest over 6 years ago in Jira 2 Shipped

Ability to "lock" a custom field, so no user can edit it

Some of our fields in Aha are solely dictated by the field in Jira, for example Status. Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrit...
Guest over 4 years ago in Jira 3 Shipped

Support JIRA issues being unassigned

If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Danny Archer over 8 years ago in Jira 2 Shipped

Support for an Aha! Initiative to create/map to Epics across multiple JIRA Projects

The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic. Simple example: Fredwin Cycling has an Epi...
Matt Case over 8 years ago in Jira 3 Shipped

Provide ability to map Created by user to Reporter field in the JIRA integration

When sending or linking a Aha feature to a Jira Epic the system uses the name of the person who created the Jira integration record instead of the user who created the epic. This results that all Jira issues now show up as Reported By with the nam...
Guest over 6 years ago in Jira 5 Shipped

Scorecard integration with JIRA business value

It's helpful for the scrum teams to not only see the Aha rank but also the business value associated with the scorecard. Integrating scorecard with JIRA Business Value is beneficial to members of the teams as well as reporting on the business valu...
Guest over 8 years ago in Jira 3 Shipped

Turn off 2-way synch for specific custom fields sent to Jira

Up until recently, custom field data was sent one-way Aha to Jira. For certain fields, we prefer the data sent one-way. We want to be able to send information such as business goals so that people using Jira can understand more about what's tryin...
Avigail Ehrenhaus over 8 years ago in Jira 0 Shipped