Skip to Main Content
ADD A NEW IDEA

Jira

Showing 245 of 8635

Support Movement of Requirements to Different Features in Other Workspaces

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
Anh Truong about 3 years ago in Jira 1 Future consideration

Allow 2-way integration to Jira FixVersion/s field from text field

Instead of having to integrate Aha! Release to Jira FixVersion/s, let Aha! text fields specify the name of a version and have it update the FixVersion in Jira based on a matched name. If no matched name exists, then throw an integration error just...
Jor Bratko about 3 years ago in Jira 0 Future consideration

use Jira credentials of the user to record changes in Jira

In the Aha! user profile, request the Jira credentials of the user. When making updates to Jira tickets, use these credentials so that we can see in the JIra ticket who actually mae the update. Kendis does this.
Guest about 3 years ago in Jira 0 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 about 3 years ago in Jira 0 Future consideration

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox 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

Add the "[Updating]" tag to Integration Reports where applicable

When you make a change to an Integration being used as a template by other workspace/integrations, while the update is progressing through the dependent workspace/integrations sometimes you see an "[Updating]" tag next to the name in the left navb...
Jor Bratko about 3 years ago in Jira 1 Future consideration

Jira integration reset

In some cases depending on workflow stories created in JIRA prior to an Epic being linked in Aha do not flow to the aha record. In this case we would like to have an option to not only resend the epic record values but also all the linked records.
David G about 3 years ago in Jira 0 Future consideration

Add support for Jira transition webhooks

Jira has two kinds of webhooks: Event webhooks that are triggered when a Jira event happens, for example an issue is updated. This is supported by the Aha! Jira integration Transition webhooks that are triggered when a Jira issue changes status. T...
Guest about 3 years ago in Jira 0 Unlikely to implement

Add "Select all" option to Integration Updates page

As a user, I want the ability to "select all" updates on the Integration Updates page, so that I do not have to select each change to send manually. When the user has set up integrations on a workspace, if there are issues with some of the integra...
Harrison Hopkins over 3 years ago in Jira 3 Already exists