ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 167 of 6678

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case:Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter 2 days ago in Jira 0 Future consideration

Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe 18 days ago in Jira 0 Future consideration

Ability to apply a Jira Integration Template to an EXISTING Jira Integration but only have it update the URL and Jira Login/Password settings

We had a very large number of Jira Integrations created before we had central administration of our Aha application. I need to apply a Jira template to these integrations so that the URL and password can be managed from a central person, but if I...
Guest about 1 month ago in Jira 0 Future consideration

Jira Integration of custom calculated field

We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release ...
Russell Roach about 1 month ago in Jira 0 Future consideration

"Do you want to sync features as well?" (for Jira/Aha integration)

In my organization we need to sync features and releases in Aha to two different Jira projects. One project receives 100% of the features and releases - perfect 1:1 sync. But the other project is only for features that rely on the design team. So ...
Byrne Reese 4 months ago in Jira 3 Unlikely to implement

Add support for Jira Portfolio "Team" field

Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
Scott McLean 5 months ago in Jira 0 Future consideration

Show Integration Errors Next To Integration Link

So often tickets stop syncing between JIRA & Aha! for one reason or another and yes, I understand there is an Integration Updates modal, but when you are working in a ticket, I should get a little error icon next to the link, in the record, if...
Robyn Diamond 5 months ago in Jira 0 Future consideration

When importing records from JIRA, allow Aha! to overide the directionality of fields configured in the integration

I have a JIRA 2.0 Integration with Aha! Features mapped to Epics in JIRA.I set the directionality of the name and description fields to be one way from Aha! to JIRA. Other fields can be mapped as required.When I perform an import from development ...
Justin Woods 5 months ago in Jira 2 Future consideration

Flag Feature/Story as had been deleted from integration

While I understand the desire to never delete a feature or story either in Aha or the integration partner (Jira in my case). I would like to see a feature that flags the deleted item in Aha as being removed. This would allow me to manually review ...
Kenny Burnham 5 months ago in Jira 0 Future consideration

Product Line initiatives linked back to Jira Epic

We have the following workspace hierarchy;Product Line AProduct BProduct CEach Product is setup to integrate with a different Jira Project.If I create a feature in Product C and link it to an initiative in Product Line A, the following happens:A U...
Bill Simakis 7 months ago in Jira 0 Future consideration