Jira

Showing 104

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

34 VOTE

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 from Aha an...

Guest almost 10 years ago in Jira 7 Shipped

25 VOTE

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 7 years ago in Jira 2 Shipped

9 VOTE

Warn when settings changes impact integration

When adjusting settings that are referenced in an integration, there is no warning that integrations will be impacted and users are not guided to update their integration settings. There are two main settings that result in notable issues in the i...

Madeleine Black almost 3 years ago in Jira 0 Shipped

17 VOTE

Ability to see more than the last 200 logs in Aha-Jira Integrations

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...

Guest over 5 years ago in Jira 2 Shipped

29 VOTE

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

29 VOTE

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

3 VOTE

Include Record IDs when logging Update Record sync errors

What is the challenge? When users use the "Update Records" action in the Jira integrations, sync failures are logged as Sync errors without mentioning which record failed to update What is the impact? Users are not able to troubleshoot and address...

Stephanie Lechner 12 months ago in Jira 0 Shipped

7 VOTE

Pop-up / indicator for new integration updates

Each of our workspaces is integrated with Jira, but often our POs question why things are missing and feel that the two applications are not always kept in sync properly despite having both the incoming and ongoing changes set to 'approve automati...

Guest over 2 years ago in Jira 2 Shipped

16 VOTE

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 overwrite...

Guest over 5 years ago in Jira 3 Shipped

Share your product feedback

Please enter your email address

FILTER BY CATEGORY