Jira
Sort by:
Trending
Status:
Showing 265
3
VOTE
Integration with JIRA needs better Error handling support
Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
1
Future consideration
4
VOTE
Link user stories (requirements) in JIRA when under the same epic (feature)
We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
2
Future consideration
1
VOTE
4
VOTE
History of items created via integration
In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
1
Future consideration
3
VOTE
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
2
Future consideration
1
VOTE
Calculate Epic Completion Based on JIRA Epic Completion
The options to calculate the completion of an epic in Aha is only based on user stories, but there are other items in JIRA that determine how complete an epic is. It would be helpful to have the progress bar completion automatically reflect whatev...
0
Already exists
4
VOTE
Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited
In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
0
Unlikely to implement
2
VOTE
4
VOTE
Allow users to name "Send To JIRA" when multiple JIRA projects are integrated
Allow users to name "Send To JIRA" when multiple JIRA projects are integrated
Currently, I have three JIRA projects integrated to a single AHA product:
LCI TEAM
METHD
UXH
Currently, these three projects show up as
Send to JIRA
Send to JIRA
Sen...
5
Already exists
2
VOTE
Provide options to prevent Sending over to Jira via integration if Status is not equal to a specific status
We need a way to prevent an end user from selecting the option in Integrations to Send to Jira unless the Status = Open. With it set to any other status, it causes Integration issues. We dont want to have to set up approvals to verify this. Just w...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved