Jira
Sort by:
Trending
Status:
Future consideration
Showing 180
1
VOTE
Ability to import JIRA labels to Aha Requirement Tags
What is the challenge? Unable to import JIRA labels to Aha Requirement Tags What is the impact? DSG tracks in JIRA Stories which business silo owns the work with Tags and tags if the work is carry over from a previous springs. DSG needs those tags...
0
Future consideration
1
VOTE
Sync Aha! feature date range to Jira associated sprint date range
What is the challenge? The product team manages the roadmap in Aha! and the dev team manages the development in Jira. Stories sometimes slide from one sprint to another and the date range of the release is not up to date with the reality What is t...
0
Future consideration
6
VOTE
Improving handling when Jira users change issue type across record hierarchy
Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
0
Future consideration
19
VOTE
1
VOTE
Allow indent with checkboxes in description
What is the challenge? We use checkboxes for our Acceptance Criteria (AC). Sometimes, it makes sense to add additional detailed ACs under a bigger AC. We use an indent for this, however, after Jira sync, these indents are removed. What is the impa...
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
12
VOTE
Show custom field names on integration errors
When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
1
Future consideration
8
VOTE
Show required fields in integration mapping
When setting up an integration, it would be helpful to have a way to be prompted to map required fields in Jira. Currently, it is possible to create an integration that does not have field mappings for required fields in Jira. This causes the inte...
1
Future consideration
8
VOTE
Do not allow requirements to be mapped without a Links To relationship set
It is possible to create an integration where you have requirements mapped to a Jira record type, and where you have no Links To relationship established to a parent record in Aha! This results in import errors where requirements cannot be importe...
0
Future consideration
15
VOTE
Product Line initiatives linked back to Jira Epic
We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved