Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My ideas: Jira

Showing 263

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 29 days ago in Jira 4 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 7 months ago in Ideas / Jira 4 Planning to implement

Reduce list for initial integration to Jira

What is the challenge? Recently, there was a change that happened that made the list of integrations very long. The option when sending something to Jira initially used to show each option, plus 1 option to Link with existing record. Now the Link ...
Guest 8 days ago in Jira 0

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 2 months ago in Jira 0 Planning to implement

Raise authentication errors from the update configuration process to the integration log

What is the challenge? Authentication issues are not called out when they occur during the reload configuration process. What is the impact? The user thinks they have successfully reloaded the configuration from Jira but the authentication may fai...
Mark Crowe 16 days ago in Jira 0 Future consideration
175 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

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 about 1 month ago in Jira 0 Future consideration

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 about 1 month ago in Jira 0 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

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