Jira
Sort by:
Trending
Status:
Showing 261
18
VOTE
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.
5
Future consideration
1
VOTE
Automatically push Epics/Features in Aha! to JIRA
What is the challenge? As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I ...
0
Future consideration
1
VOTE
Flag a broken JIRA integration to the Aha! admin so it can be resolved
What is the challenge? As an Aha! admin, I want to ensure the JIRA to Aha! integration flags errors to me proactively (via email would be great), so that errors in the integration setup can be immediately addressed. What is the impact? As an Aha! ...
0
Future consideration
3
VOTE
Allow editing to wiki-rendered fields in Jira
Who would benefit? Jira integration users What impact would it make? Currently Jira is sending broken formatting when fields leverage wiki-rendering with tables How should it work? If a user makes an edit to a table in Jira on a wiki-rendered fiel...
1
Future consideration
5
VOTE
5
VOTE
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 ...
0
Future consideration
7
VOTE
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...
1
Future consideration
15
VOTE
JIRA integration needed at the portfolio and product family levels.
We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
2
Future consideration
2
VOTE
Automatically update roll-up release name in integrations
Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
0
Future consideration
25
VOTE
Allow To-Do's to be mapped to JIRA Issue Types
We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
5
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved