ADD A NEW IDEA

My ideas: Jira

Showing 171

Calculated mapping of number fields in integration with Jira

We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...
Jor Bratko almost 2 years ago in Jira 0 Future consideration

Make JIRA webhooks URL specific

Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
Guest about 2 years ago in Jira 0 Future consideration

Enable external link handling for Jira and other integrations

Jira has a native link handling functionality that displays links in-line on issues. To recreate the same behavior, I have to create a custom field for the link to target (meaning I end up with a bunch of extra fields) and need to reciprocate acro...
Yancey Larochelle-Williams over 2 years ago in Jira 0 Future consideration

Jira integration needs to include Tempo Team field

This is a blocker for us.
Tracey locke over 2 years ago in Jira 1 Future consideration

JIRA integration to track correct users in history of issues

Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
Austin Churchill almost 3 years ago in Jira 1 Future consideration

Send events before deletion

We currently sync a field in Aha! to Jira when a record is created. We’d like to clear that field if the record is deleted from Aha! I’m looking to send an update to the field or set an event trigger to make a note that the field value has changed.
Yancey Larochelle-Williams over 3 years ago in Jira 0 Future consideration

Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status

We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
Guest over 3 years ago in Jira 1 Future consideration

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 over 3 years 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 almost 4 years 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 developmen...
Justin Woods about 4 years ago in Jira 2 Future consideration