Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 268 of 9346

Integration error: "Review the errors" link should show the error

When sending an Aha record to Jira and there’s an error, a message appears with a “Review the errors” link. This opens up the Integration Updates modal. From this page, it's not obvious that you can view the error by hovering over the info icon to...
Brian Trombley about 4 years ago in Integrations / Jira 0 Future consideration

Support mapping Asset object fields through Jira integration

Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
Stephanie Lechner over 1 year 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 over 9 years ago in Jira 8 Unlikely to implement

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 almost 8 years ago in Jira 3 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

Auto Resend all Fields per release

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
Guest over 6 years ago in Jira 2 Future consideration

Map Created By User from Jira

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Guest over 2 years ago in Jira 1 Already exists

Aha Jira Integration mapping need to include the new Jira Object Capability

What is the challenge? Could not use the new Jira object in the mappings What is the impact? Teams want to group similar Epics in capability. without this, we can group them for tracking Describe your idea We already have Aha Integration to Jira i...
Guest 6 months ago in Jira 0 Future consideration

Including Dependencies in Jira integration at requirements/story level

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S over 3 years ago in Jira 0 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 over 2 years ago in Jira 0 Future consideration