- changed status to resolved
Can jira policy be enforced for service accounts?
Issue #220
resolved
When an ssh key has been added to a repository (or project) and I try to push with a valid Jira ticket in the commit message, I get an error that the ticket does not exist.
I don’t get this error if the ssh key is applied to my user.
I use OAuth With Impersonation in my Jira Application Link.
I know I can use the Serivce account exemption, but I’d like to still validate those commit messages.
Would it be possible to include a “run as” or “jira account” to attempt to impersonate when making the connection to Jira so that service account commits will be correctly validated?
Comments (1)
-
repo owner - Log in to comment
Fixed in Control-Freak v2020.08.04. Look for the new "Jira-Impersonation" config options:
Jira Impersonation Account: <email>
Jira Impersonation - When To Use: { Always | Service-Acounts-Only | Never }