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 transition. We need to be able to also do this in Aha and send that information to Jira. The current way that Aha works with Jira doesn't support this and when a record is closed in Aha it errors out and leaves the Jira issue open.
Support resolved date
The resolved date in Jira is set when an issue is closed. This field is not editable though so it doesn't show up as an available field for mapping in our Aha / Jira integrations. We would like Aha integrations to support this and other calculated fields as well.Support
Percent complete roll-up
Percent complete roll-up currently uses an average of the percent complete values of the child records. This results in inaccurate percent complete values in the parent records.
In our Jira integration, we map the status to both the Jira status as well as the Jira resolution. So, if an Aha status is Will Not Implement, we map that to both the status and to the resolution fields.
I agree with all comments Marcie brings up. An auto update to Aha! on Jira Stories is a must. It should be configurable to update at certain intervals, certainly on launch of Aha!.