Jira
Sort by:
Trending
Filter by:
Status
Showing 265 of 9041
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
8
VOTE
Integrating with a specific Jira board
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
1
Future consideration
3
VOTE
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
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
5
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
17
VOTE
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
8
VOTE
Urgent Jira Integration Needs: Resolution, Resolved Date & Percent complete
These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...
2
Future consideration
14
VOTE
Add support for Jira Portfolio "Team" field
Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
1
Future consideration
5
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
© 2024 Aha! Labs Inc.•All rights reserved