ADD A NEW IDEA

My ideas: Jira

Showing 254
133 VOTE

Integrate ideas with Jira

What is the challenge? Companies that use both Jira and Aha! ideas must go through extra steps to send information between the two systems. For example, if a small fix comes in as an Aha! idea, it must first be promoted to a feature or requirement...
Kelly Sebes 4 months ago in Ideas / Jira 3 Future consideration

Record successful updates in Aha! from Jira "update records" action

What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
Stephanie Lechner 20 days ago in Jira 0 Future consideration

Include Record IDs when logging Update Record sync errors

What is the challenge? When users use the "Update Records" action in the Jira integrations, sync failures are logged as Sync errors without mentioning which record failed to update What is the impact? Users are not able to troubleshoot and address...
Stephanie Lechner 20 days ago in Jira 0 Planning to implement

Allow Jira Team Custom Field to Integrate with Aha! Predefined Choice Fields

What is the challenge? The Jira Team field in Jira can only be mapped to string-based fields like notes and text fields. There is no way to configure this field with predefined choices that match the available teams in Jira. What is the impact? Us...
Justin Paulson 25 days ago in Jira 0 Future consideration
167 VOTE

Dedicated Integration User

It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...
Guest over 7 years ago in Integrations / Jira 16 Future consideration

Sync initial estimate field in integrations

I am able to sync my detailed estimate field in Jira integrations, but not initial estimate.
Alina Mavis over 1 year ago in Jira 5 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 n...
Russell Roach almost 4 years ago in Jira 3 Future consideration

Epics that aren't selected for import in the Import list should be saved or maintained in Aha for later import.

What is the challenge? Once an epic is ignored on the import list in Aha it cannot be retrieved to be imported at a later date. What is the impact? Doubles the work of having to create the corresponding feature for the epic in Aha and then link it...
Noor Akhtar 5 months ago in Jira 0 Future consideration

Allow integrations such as Jira at the Product Line level

Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Steve C over 2 years ago in Jira 5 Planning to implement

Manual Sending of Requirements to integrated development tool

Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R over 1 year ago in Jira 2 Future consideration