behaviours plugin behaving erratically in JIRA 6.1.5

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

2 answers

@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"

0 votes

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

26,386 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you