JIRA Behaviour Plugin

Hi,
We have created a custom field called "Special Release" and defined a condition using Behaviour plugin where the field is editable only for Project Manager role. But when I login as Business Analyst, initially the field is in read-only mode but when I click on Configure fields-->Check off Special Release and again Check Special Release the field is editable now.
We have started using this plugin and now we found this issue and not sure what to do. Please help

  • We have many roles and now anyone can edit any fields because of this issue. Please advise!

5 answers

0 vote

what version of jira and the plugin? Also out of interest, why did you not use any labels referencing the plugin?

JIRA Version 6.0.3 and Behaviour plugin version 0.5.10. I am sorry. I am new to Atlassian Answers so not sure how to use labels.

Please help us. Due to this issue all the roles can edit the read-only fields.

0 vote

It's a bug, see JBHV-304

Is someone working on this bug? Any idea when this issue will get resolved. We have many users facing issues and we are really looking to resolve this issue or any workarounds. We have many projects and many custom fields associated with this plugin and now we are not sure what we should do. Can you advise please?

What are the issues that they are facing?

We have read-only fields for specific project roles. Due to this plugin issue, when the users select configure fields, uncheck and check custom fields the read-only fields are editable for all the project roles. Can you advise any workarounds? We have almost 750 users and getting 'n' number of emails escalating about this issue. Any help on this is greatly appreciated.

what are they escalating, that they can write a field that they should not be able to? How come this suddenly became an issue.

Just an idea of an workaround: make the field read-only for everyone. Allow edit through a workflow transition only Project Manager role is allowed to. You will need an other field on that workflow screen to copy its value to Special Release field with a post function.

We have many users facing issues and we are really looking to resolve this issue or any workarounds. We have many projects and many custom fields associated with this plugin and now we are not sure what we should do. Can you advise please?

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

244 views 1 18
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