I want to make restriction for edit summary field to be editable only for same roles for the whole projects.
I used behaviours to make the field readOnly with expect condition to that role it works but it will be restricted for the whole (Create, view and edit).
There is another way to do this ?
There's a way to achieve this. Not the most elegant solution, but it works.
1) Remove 'Summary' field from issue 'Edit' screen
2) In your workflow create a GLOBAL transition, that lead to ITSELF. That way it will be available in every status, but won't change the current status once used.
3) Add a screen to that transition with 'Summary' field
4) Add all neccessary conditions to that transition, to make it available only to certain project roles.
Now your 'Summary' field will be editable ONLY through that transition. Transition conditions will make sure it's only available to required project roles.
Hope this helps.
Behaviors could be the solution, but it'll require some fine tuning, like specifying actions (screens) where you want 'Summary' to be editable for everyone (like Create screen). Other than that I don't really see a problem with behaviours. Please let me know if you need help with the code.
Yes, I'm focusing on behaviours, i added a behaviour to the summary filed I make it read-only with a condition for some roles and I mapped for all the projects the problem now I didn't get the part to make this happen only on the edit screens because in this way even when you create the issue you must be part of the role users.
Do I'm on the right way?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events