Jira integration - Allow Jira account username/password modification per workspace when using a shared integration template

What is the challenge?

We have a shared template across all of our Jira integrations to manage the configuration globally. However, using a global template forces us to have the same integration username (mine, the Aha!/Jira admin) across all projects. On the Jira side, it then appears like I am making all the changes rather than product manager who owns the workspace and actually is making the changes in Aha!.

What is the impact?

The impact is that in Jira, any Aha! changes are tied to one person's account for all projects, and this makes tracking down who made what changes in Jira problematic. Moreover, it falsely attributes the change to the wrong user (whoever is set up to run the global automation through).

Describe your idea

Ideally, regardless of the account used to establish the integration, the person who actually makes the change could be pulled in to Jira. If that is not possible, the secondary solution would be to allow a different account set up for each workspace integration, while still allowing use of a global template for all other fields.