Skip to Main Content
ADD A NEW IDEA

Jira

Showing 85

When creating feature and selecting feature type "bug" creates issue in Jira as "story"

This is really important to be able to map these when creating new features in releases for me.
Nate Hunter over 8 years ago in Jira 6 Shipped

Disable JIRA and Aha! Comment Sync

We are getting ready to share Aha with key stakeholders around the company, and we do not want to share the inside engineering chatter with the rest of the company. We have comments in JIRA that should not be broadly available. I would like to be ...
Cameron O'Rourke over 8 years ago in Jira 4 Shipped

Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. It would be great to also access the Resolution status from Jira to handle this c...
Guest over 8 years ago in Jira 17 Shipped

JIRA Integration at Product Line Level

As an Aha Administrator, I have a large number of products that link to one JIRA project and having to setup the same integration over and over again for these products is time consuming and painful. Setting up a JIRA integration at a higher level...
Guest over 8 years ago in Jira 1 Shipped
136 VOTE

Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match

If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
Guest over 8 years ago in Jira 22 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

Allow customization of on-prem Jira link displayed in Feature details so that link actually works

High-level: The URL that is used for integration with our on-prem Jira implementation is not the same as the URL that we use while on our network. Consequently, clickin on the Jira link within any feature takes us to nowhere. This enhancement re...
Guest over 8 years ago in Jira 3 Shipped

I need "Master Release" to appear in Jira

We use Master Releases when we have multiple products shipping together. I need the Master Release name to appear in Jira for reporting. I'm flexible as to how this can be done. Maybe a way to create a custom field on the feature level that auto-...
Avigail Ehrenhaus over 8 years ago in Jira 0 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 over 8 years ago in Jira 7 Shipped

Track effort (estimates) to prepare features for JIRA separately

When Aha!-JIRA integration is enabled, updating the features estimates on one of the tools, will cause an update on the other. We suggest to have the possibility to un-map the estimates fields between the 2 tools. So updating on one tool won't af...
Guest almost 9 years ago in Jira 1 Shipped