Skip to Main Content
ADD A NEW IDEA

Jira

Showing 249

Map to a persona name value in integrations

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping
Barnett Klane almost 5 years ago in Jira 3 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 about 4 years ago in Jira 1 Likely to implement

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 almost 3 years ago in API / Jira 1 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 2 years ago in Jira 1 Future consideration

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.
Guest 11 months ago in Jira 1 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

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 more filters to integrations import

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer 8 months ago in Jira 0 Already exists

When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.

The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin almost 6 years ago in Jira 5 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