Pushing tags still checking JIRA

[Former user]

Even though applying the JIRA policy is turned off for tagging in our repo, our jenkins builds are occasionally failing to do a push because the user doesn't have access to JIRA.

Also, the tag in question contains no tickets, however previously merged tickets are being referenced for being checked.

11:56:57  + git tag -f -a 126.0.0 -m '[NO-JIRA] Tagging version 126.0.0'
11:56:57  + git push origin -f 126.0.0
11:56:58  remote: Control Freak v2021.07.18: Commit messages on "126.0.0" must reference valid JIRA tickets,        
11:56:58  remote: 
11:56:58  remote: Control Freak v2021.07.18        
11:56:58  remote: -----        
11:56:58  remote: Commit messages on "126.0.0" must reference valid JIRA tickets,        
11:56:58  remote: but Bitbucket cannot access JIRA to see if "[ATS-25737, ATS-26430, ATS-26492]" exists.        
11:56:58  remote: Your Bitbucket account is missing OAUTH credentials into JIRA.    

[Julius Davies [bit-booster.com]]

Control-Freak v2022.08.04 provides a new "Jira-Impersonation" issue which allows Jenkins builds to properly connect to Jira now, solving this issue.

In particular, look for this config option:

Jira Impersonation - When To Use

[x] - For Service Accounts Only