Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Scriptrunner pre-hook - Require commits to be associated with a JIRA issue

Kailash Subramanian May 15, 2019

For one user, this hook is complaining that the assignee on the JIRA issue doesn't match the user who is pushing the commit associated with a JIRA id. Lot of other users are able to push the commits with valid JIRA ids without any problem. 

We have tried several things but not able to figure out what the issue is. When we run the JQL query on the JIRA side for this particular user, it pulls up this JIRA issue correctly. If we drop the condition "assignee = currentUser()" from the JQL in the pre-hook, the user is able to push the same commit.

We have checked the username in JIRA and it matches exactly (including case) the username on the Bitbucket side. Also, we had the user try the same from another workstation and the problem still exists. Enabled the GIT debug but it didn't throw any light either. 

Does anybody have any tips or guidance about how to troubleshoot/resolve this issue? Soon, we are going to roll this out to larger team and would like to know ways to troubleshoot this issue.

 

Regards,

Sam

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events