Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

My ideas: Jira

Showing 222 of 7589

Provide warning for Jira integration when integrating % complete without child records being linked

When configuring a Jira integration, you can map the Epic % complete field in Aha! to the Epic % complete (issues completed) field in Jira. According to https://www.aha.io/support/roadmaps/strategic-roadmaps/roadmaps/visualize-progress-on-roadmaps...
Emily Yankush 19 days ago in Jira 0 Future consideration

Allow Jira Epics to Integrate

When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Guest about 1 month ago in Jira 0 Future consideration

Improve warning for integrations "Update Records" action

For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
Emily Yankush about 1 month ago in Jira 0 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 2 months 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 3 months ago in Jira 0 Future consideration

Provide error if the Jira webhook "Exclude body" checkbox is selected

When configuring a webook in Jira, there is a checkbox: ☐ "Exclude body" Request with empty body will be sent to the URL. Leave unchecked if you want to receive JSON. If someone accidentally checks that, Aha! won't get any updates. There is no log...
Emily Yankush 3 months ago in Jira 0 Planning to implement

Show required fields in integration mapping

When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
Madeleine Black 4 months ago in Jira 1 Future consideration

Do not allow requirements to be mapped without a Links To relationship set

It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
Madeleine Black 4 months ago in Jira 0 Future consideration

Improve visibility of integrations update modal

When users set up an integration and select "auto import records", they are not immediately aware that some records will not just automatically import into Aha! (i.e. those that don't have a parent record that is sync'd). These users are not able ...
Madeleine Black 4 months ago in Jira 0 Future consideration

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black 4 months ago in Jira 0 Future consideration