Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Jira Integrations: Map Aha Releases to a custom Jira Version Field
Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...
Kyle Shannon
11 months ago
in Jira
0
Future consideration
Allow one-way mapping of calculated/read only Jira fields into Aha
Who would benefit? Aha users needing to see Jira data that is not editable in Jira What impact would it make? In our case, allow us to use engineering estimation data in Aha scorecard calculations. How should it work? The current Aha-Jira integrat...
Mike Wachal
about 1 year ago
in Jira
0
Future consideration
Add option to show additional columns/fields in "Integration updates" window for Jira
The "Integration updates" window currently only shows the issue summary of incoming issues. Presumably the JSON payload being received by Aha contains the full set of information for the incoming issue ... it would be incredibly valuable to be abl...
Gene Lewin
about 1 year ago
in Jira
0
Future consideration
Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder
over 1 year ago
in Jira
1
Future consideration
Allow Jira Integration to synchronize External Release Dates
In Jira, we track external Release Dates. Aha does not allow external release dates to be synced. This means our Jira is reporting inaccurate information.
Guest
over 1 year ago
in Jira
0
Future consideration
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...
Guest
over 1 year ago
in Jira
0
Future consideration
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...
I R
over 1 year ago
in Jira
0
Future consideration
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 ...
Emily Yankush
over 1 year ago
in Jira
0
Future consideration
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.
Eric Hutchins
over 1 year ago
in Jira
0
Future consideration