We are using JIRA 6.3.13 and ScriptRunner 3.0.7.
BEFORE installing/enabling the ScriptRunner we can create issues in a specific project.
AFTER enanbling ScriptRunner, some fields are LOCKED when we want to create issues.
Any ideas ? I have also attached the JIRA logfile ()
it looks like your workflow is not allowing you to edit issues: 2015-02-11 12:13:35,381 http-bio-8080-exec-65 INFO thomassn 733x308093x1 fg1fg2 172.16.111.66,172.16.184.192 /browse/SW-817 [atlassian.jira.security.WorkflowBasedPermissionManager] edit granted by permission scheme but DENIED by workflow
Hi Alejo, we indeed have permission granted/denied in that workflow (see screenshot attached), but this behaviour happens when you simply click the "Create" button (in order for the Create Screen to popup). So I should expect that at that time the users that have "create issue" permissions (according to the SW Factory permission scheme) are allowed to create issues. In the "Save as Draft" transition (ie. the FIRST transition after the intial "create", we are granting edit and assign rights to specific roles: ira.permission.edit.projectrole.1 10100 jira.permission.edit.projectrole.2 10000 jira.permission.edit.projectrole.3 10200 jira.permission.assign.projectrole.1 10100 jira.permission.assign.projectrole.2 10200 but I AM in that role, so strange that those fields are locked only when the Scriptrunner plugin is enabled. After disabling the scriptrunner plugin, everything works like it should, so it seems to me that the ScriptRunner reads the permissions "too early" (?) or something...
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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