Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 260

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 2 months ago in Jira 4 Future consideration

Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to

What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...
Stephanie Lechner about 1 month ago in Jira 0 Likely to implement

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 3 months ago in Jira 0 Planning to implement
192 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 almost 8 years ago in Integrations / Jira 16 Future consideration

Map custom release field in Jira integration

Currently the Jira integration doesn't allow users to map the custom release field, on records like features. We would like to be able to map this field and ideally to map it with a custom versions field in Jira. The two fields should be able to m...
Diane Metzger 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 almost 2 years ago in Jira 5 Future consideration

Add 'Send to integration' automation action for Aha! Ideas <> Jira integration

What is the challenge? As PMs review ideas submitted to Aha! there may be ideas that need to be sent directly to Jira — thinking about bugs that are reported through an ideas portal. What is the impact? Those ideas need to be reviewed alongside al...
Justin Waldorf 26 days ago in Ideas / Jira 0 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 over 4 years ago in Jira 3 Future consideration

Sync comments between Jira & Aha!

What is the challenge? Unable to Sync deleted and edited comments between Jira and Aha! What is the impact? Syncing deleted and edited comments between Jira and Aha! is crucial to maintaining accurate and up-to-date communication across teams. If ...
Prachi H 4 months ago in Integrations / Jira 1 Future consideration

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