Skip to Main Content
ADD A NEW IDEA

Jira

Showing 250

Show custom field names on integration errors

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley about 3 years ago in Jira 1 Future consideration

Integration error: "Review the errors" link should show the error

When sending an Aha record to Jira and there’s an error, a message appears with a “Review the errors” link. This opens up the Integration Updates modal. From this page, it's not obvious that you can view the error by hovering over the info icon to...
Brian Trombley about 3 years ago in Integrations / Jira 0 Future consideration

Ability to remove stories that are in the integration from Aha!

Often times we only want a subset of what's in Aha! in our JIRA project. In some cases, when things get deprioritized, we want to remove them from JIRA but keep them in Aha! Would love the ability to do that FROM Aha! because keeping things in syn...
Guest about 3 years ago in Jira 0 Future consideration

Aha Roadmaps- Provide ability to integrate with Themes

Right now you cannot link themes and epics from Jira to Aha- Themes are detached from Epics
Guest about 3 years ago in Jira 0 Future consideration

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 over 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 over 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 over 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 over 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 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