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: |
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
Thanks for confirming the issue Zulfadli.
Do you know if there is anywhere I can create a bug for the behaviours plugin?
Mick
You might want to test it again on several settings as well. As for reporting, should be in the following link:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I seems to have the same problem when setting it for Read-only except Project Lead yesterday. Tried on version 0.5.2
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.