Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 273

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

Fix field population in Aha/Jira integrations to only rely on email address or other specific data

Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Guest about 3 years ago in Jira 1 Future consideration

Project level automation with Jira

Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest almost 3 years ago in Jira 0 Future consideration

Support mapping JIRA Tempo Account field

When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest almost 10 years ago in Jira 8 Unlikely to implement

Populate Jira Components via Integration

Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest over 2 years ago in Jira 0 Future consideration

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest about 8 years ago in Jira 3 Future consideration

Allow to manually push a Jira Theme to Aha as an MF ( without the need of a ready MF on Aha side)

What is the challenge? Currently we have cases where RnD would open a theme (we categorize it) , and that is for mostly themes with technical nature. as such PM will not initiate them, but we still want the PM to be aware of them in planning and p...
Alon Sabban 6 months ago in Jira 0 Future consideration

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
Guest over 10 years ago in Comments / Notifications / Jira 1 Unlikely to implement

Send over images as correct size when integrating from Aha to Jira

What is the challenge? Steps: Create a feature in Aha and add a screenshot within the description. Send the feature to Jira. Result: In Jira, the image has a bunch of white space to the left and right of the image. So the image is small in Jira. W...
Guest 6 months ago in Jira 0 Future consideration

Integration Jira - Enable links across projects

I would like to be able to integrate "Epics" from different "Projects" in Jira under common "Themes".
Guest over 2 years ago in Jira 1 Already exists