Jira
Sort by:
Recent
Status:
Future consideration
Showing 168
1
VOTE
1
VOTE
Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
0
Future consideration
2
VOTE
Use Custom Table data in Integration with Jira
Need to functionality to include Custom Table fields in the integration mapping. We created a new table for Aha Roadmaps for Program Increments. The table is linked to both Epics and Features, to simplify the reports (same value for both). The cha...
0
Future consideration
2
VOTE
Sync Delivery Risk manual flag to Jira "Flagged"
In Aha!, if you have enabled 'Delivery risks', one of the things you can do is manually set a flag on a Feature (or Epic or Requirement). In Jira, you can also 'Flag' issues similarly. Aha!: https://www.aha.io/support/roadmaps/strategic-roadmaps/c...
0
Future consideration
15
VOTE
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
2
Future consideration
11
VOTE
Support updating JIRA Integration Links by csv upload
While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...
0
Future consideration
1
VOTE
Allow Mapping of Requirement Type from Jira to Aha!
Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...
0
Future consideration
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
Populate Jira Components via Integration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
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