nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Behaviour Plugin

Karthick Sambas

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!

Accepted answers

All comments

JamieA

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

Karthick Sambas

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.

Karthick Sambas

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

JamieA

It's a bug, see JBHV-304

Karthick Sambas

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?

Karthick Sambas

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

What are the issues that they are facing?

Karthick Sambas

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

behaviours