When the Push Check plugin has been enabled it's not possible to push without authorising the plugin to use JIRA.
The error displayed directly from git is:
[Syntax check] Permission problems. You are not allowed to execute the requested JIRA Rest action. Please ensure that authentication method OAuth is enabled. Also the OAuth options "Allow 2-Legged OAuth" and "Allow user impersonation through 2-Legged OAuth" should be set on both sides of the application link (in- and outgoing connections) (CredentialsRequiredException: You do not have an authorized access token for the remote resource.)
Did you face such problem, how can you force the plugin to authorize within JIRA per each individual user?
Each user have to do the OAuth dance once. It is like clicking the "I Agree" button and you can't do it for someone else
You will need to do this for the standard JIRA Bitbucket integration anyway. It is not just for this plugin. And once you do it, all interactions will use the same token.
I know this is late to the party, but how exactly do we do the "OAuth dance?
I'm a sysadmin on both Jira and Bitbucket, and can push without problems, with the push check enabled. However, when a project resource, who has admin rights to the bitbucket project (but not system wide admin rights, nor admin rights on Jira), does this, he gets the error.
Any document or something I can read to help us with the OAuth dance?
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs