Behaviours Plugin not allowing Project Lead access to Edit

Michael Roff
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.
November 26, 2012

I have the following configuration with the latest version of Behaviours running on JIRA 5.1.2.

Behaviour: Edit Only

When finished view all behaviours.
General Settings
Validate Jira Requiredness
This will check your Field Config Scheme and validate required fields (before the issue is submitted).
Disabled (Enable)
Use Validator Plugin
This will check your workflow for uses of the Fields Required validator in Jira Suite Utilities, and mark these fields as required.
Disabled (Enable)
Guide Workflow
Use this setting to allow the tool to show you actions and state names when using Conditions.
<select name="guideWorkflow"><option selected="selected" value="-1">None</option><option value="jira">jira</option><option value="Action Item Workflow">Action Item Workflow</option><option value="CAR Workflow">CAR Workflow</option><option value="CLAAS Workflow">CLAAS Workflow</option><option value="Customer Complaint Workflow ">Customer Complaint Workflow </option><option value="Information Services Workflow">Information Services Workflow</option><option value="IS Support Ticket Workflow">IS Support Ticket Workflow</option><option value="Issues Workflow">Issues Workflow</option><option value="OFI` Workflow">OFI` Workflow</option><option value="Product Defect Workflow">Product Defect Workflow</option><option value="Requirement Workflow">Requirement Workflow</option><option value="Testing Workflow">Testing Workflow</option></select>
Changes saved automatically
Fields
Field: Summary
Delete
Optional (Require)
Readonly (Writable)
Shown (Hide)

Add serverside script

Conditions:
  • When:
  • Except:
    • Current user is Project lead (Delete)
    • Current user is Current assignee (Delete)
  • Add

This should restrict the Summary Field from being edited by anyone other than the Current Assignee and the Project Lead. It works for the Current Assignee, but the Project Lead does not have access.

Is this a bug in Behaviours or am I doing something wrong?

Can anyone repeat this problem?

Thanks, Mick

2 answers

0 votes
Michael Roff
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.
November 28, 2012

Thanks for confirming the issue Zulfadli.

Do you know if there is anywhere I can create a bug for the behaviours plugin?

Mick

Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 28, 2012

You might want to test it again on several settings as well. As for reporting, should be in the following link:

https://studio.plugins.atlassian.com/browse/JBHV

0 votes
Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 28, 2012

I seems to have the same problem when setting it for Read-only except Project Lead yesterday. Tried on version 0.5.2

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events