I installed the Behaviours Plugin on a locally hosted instance of 6.1.5. I need it primarily to make fields read-only. Here is a summary of when it worked and when it didn't:
Current User is Reporter |
No |
Current User is in Group |
Yes |
Current User is Project Lead |
No |
Current User is [username] |
Yes |
Current User is value of field |
No |
Current User is in Project Role |
Yes |
Current user is member of group from field |
No |
Current User is assignee |
No |
Current User is Reporter |
No |
Current User is in user custom field value |
No |
Am I doing something wrong?
Thanks
LC
This was bad, it was broken - it will be fixed in the next release, please add yourself as watcher to https://jamieechlin.atlassian.net/browse/JBHV-312
I infer from this that there was inadequate regression test coverage but also that they are rarely used, as you can check for this stuff in the server-side script.
@Jamie Echlin [Adaptavist] I'm using JIRA 6.2.1 with Script Runner 3.0.5 and I've the same issue. Do you have any idea what causes that or any workaround? I enabled logging to inspect this but log says only "user must be assignee" or "user must be reporter"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.