Jira
Sort by:
Trending
Status:
Showing 264
1
VOTE
Provide applicable error message when a Jira integration can't authenticate due to a captcha challenge issue
When attempting to set up a Jira integration, authentication can fail with a 403: CAPTCHA_CHALLENGE error we can see in the logs, but there is no applicable message on the integration-set up screen. It just says "We could not connect to your Jira ...
0
Future consideration
3
VOTE
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
0
Future consideration
1
VOTE
The ability to create a report to show if there are any pending Integration Updates rather than having to manually look for them
Simplify the ability to know if there are pending updates to either Import or Ignore by running/scheduling a report with this data by Workspace and Integration, etc.
0
Future consideration
3
VOTE
Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt
We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
0
Future consideration
2
VOTE
Ability to map Jira Web Links with Aha! URL at Integration
Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
0
Future consideration
2
VOTE
JIRA integration to track correct users in history of issues
Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
1
Future consideration
4
VOTE
JIRA Integration - allow bidirectional mapping of the "time frame" field
for those who map epics to initiatives, and like to keep their platforms bidirectionally synced as much as possible, it's possible to have a custom "time frame" field in JIRA set up to match that in Aha, yet it's not possible at the moment to bidi...
1
Future consideration
3
VOTE
JIRA integration Import of only linked epics
When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
0
Future consideration
1
VOTE
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
© 2024 Aha! Labs Inc.•All rights reserved