ADD A NEW IDEA

My votes: Jira

Showing 262

The ability to review previously ignored integration candidates and undo the ignore

What is the challenge? Once you ignore an integration candidate, it is ignored forever unless you manually import or link the ignored record. If someone ignores a record by mistake there is no recourse to review those potential errors and correct ...
Stephanie Lechner 1 day ago in Jira 2 Future consideration

Sync Jira OOTB field values

What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
Michael Tucker about 10 hours ago in Jira 0

Ability to update Jira Affects Versions field from Aha via integration

What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner 2 days ago in Jira 0

Map detailed estimates by initiative in Jira integration

What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
Kelly Fogus 3 days ago in Jira 0 Future consideration

Send ideas to 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 6 months ago in Ideas / Jira 4 Planning to implement

Allow automatic imports of child records when parent records exist in a different workspace

What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
Stephanie Lechner 6 days ago in Jira 0 Future consideration

Features and Epics should move to integrated parent Release upon updates

What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
Stephanie Lechner about 1 month ago in Jira 0 Planning to implement

Keep formatting from a Jira table

What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integration Des...
Terri Salie 15 days ago in Jira 0 Future consideration
172 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

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 3 months ago in Jira 0 Future consideration