Skip to Main Content
ADD A NEW IDEA

Jira

Showing 247 of 8599

Add better error handling for 'unhandled error exceptions'

When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
Guest 6 months ago in Jira 0 Future consideration

Update API integrations with JIRA to add Created Date and Resolved Date

We would like to be able to map the created date as well as the resolved date to fields within aha from JIRA.
Guest over 2 years ago in API / Jira 1 Future consideration

Filter noise from Jira integration logs

The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
Sandy Kobayashi about 1 year 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 over 1 year ago in Jira 1 Future consideration

Add support for Jira Portfolio "Team" field

Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
Scott McLean almost 4 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 over 1 year ago in Jira 0 Future consideration

Support JIRA issues being unassigned

If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Danny Archer about 8 years ago in Jira 2 Future consideration

Map JIRA Fix Version to Aha Release Phase

We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key ...
David Vins over 5 years ago in Jira 8 Future consideration

Product Line initiatives linked back to Jira Epic

We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis almost 4 years ago in Jira 1 Future consideration

Support of Embedding of Ideas in Confluence

As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar 8 months ago in Jira 0 Future consideration