Jira
Sort by:
Recent
Status:
Showing 245
1
VOTE
Allow Created By User Field to be Updated in UI and via Integration
Currently, there is no way to edit the "created by user" field in Aha! Even though if you go to integration mappings, it allows you to map that field with the Jira "Reporter" field and allows you to toggle the integration to "2-way", yet Aha! Supp...
0
Future consideration
6
VOTE
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
0
Future consideration
2
VOTE
JIRA Integration - Allow Changing Board
We recently had to migrate JIRA tenant to another existing one (as the result of an acquisition). Whilst I was able to just change the server address and the integration URLs pointed to the correct location of the migrated issues, the board used f...
0
Future consideration
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