At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance that we may not want to.
Rather, permissioning the other way around would be better. So, the ability to use a JIRA account with minimal user permissions that we then permission on our end to configure which JIRA projects we want to grant access to.
Without this, we cannot integrate JIRA and Aha! causing significant manual overhead and potential for human error.
|Release time frame|
The JIRA admin permission is only necessary to create a custom field in JIRA. If you create that custom field before doing the integration then no special permission is necessary for the user account used in the integration.
To create the custom field in JIRA:
Aha! will recognize this field next time you click "Test connection” and won’t try to recreate it.