JIRA Behaviour Plugin

Karthick Sambasivam September 9, 2014

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 votes
Karthick Sambasivam September 9, 2014

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?

0 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 9, 2014

It's a bug, see JBHV-304

Karthick Sambasivam September 9, 2014

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?

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 9, 2014

What are the issues that they are facing?

Karthick Sambasivam September 9, 2014

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.

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 9, 2014

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

JK
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2014

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.

0 votes
Karthick Sambasivam September 9, 2014

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

0 votes
Karthick Sambasivam September 9, 2014

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.

0 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 9, 2014

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

Suggest an answer

Log in or Sign up to answer