Skip to Main Content
ADD A NEW IDEA

Jira

Showing 245

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 about 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 about 3 years ago in Jira 1 Future consideration

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.

Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
Guest over 3 years ago in Jira 3 Already exists

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 over 3 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 almost 4 years ago in Jira 2 Future consideration

Synchronising JIRA backlog with Aha ordering

Currently I use the feature board loads - organise all my features into releases with certain priorities and I use capacity planning and it's great. And I have a JIRA integration so anything I create in Aha is pushed out to JIRA with the correct r...
Guest about 4 years ago in Jira 1 Future consideration

Sync with Jira include ability to link back to Aha Item

When configuring sync between Aha and Jira, it should include the ability to have a URL back to the associated Aha idea inserted in Jira field. This would allow Product and Engineering a better way to trace stories back to the original Features, O...
Joe Watson about 4 years ago in Jira 2 Future consideration

Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release

Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
Josh Tambor about 4 years ago in Jira 0 Future consideration

Aha Integration Status Criteria

In Integration, I am not able to choose which statuses I send and which status changes I do not. Example, captured, i do not want to send, but Aha Integration allows me to send to down stream systems with a blank mapping. Please enhance integratio...
Sasi Ravichandar about 5 years ago in Jira 0 Already exists