modify field in only one status

[Marco Campeotto]

Hello everybody,

I have a question about the possibility to modify a field only in one particular status.

I try to explain my situation with an example.


There are 4 status: A - B - C - D

for each task there are 3 Text field (multi-line wiki): Description - Main - Conclusion

I want to set the possibility to:

in status A the permission to modify only the text field "Main"

in status B the permission to modify only the text field "Description"

in status C the permission to modify only the text field "Conclusion"

in status D the permission to modify all text field

 

is there the possibility to change the permission of edit field in post-function or thanks scriptrunner?

thanks,
Marco

[Joe Pitt]

You can do it with transitions from that status you want to change it in only showing the field in the transition screens and View Screen. The transition could go back to the same status or forward. I don't have experience with scriptrunner

[Marco Campeotto]

Hi @Joe Pitt,

in the transition screens, you see the field if you click to the button of transition...

i want the possibility to edit and re-edit the "main", "description" and "conclusion" fields many times before to move the issue in the new status (and so using the transition screens)

that's why i would like to "edit"/change the permission to edit field for each status.

there are other fields like labels, components.... and these fields were edit during the creation of issue... but in the status D i want the possibility to edit these fields but not during the status A-B-C.

[Joe Pitt]

You can't change edit permissions on the fly in the base code or in any plugin I'm aware of.  If you want certain roles to be able to edit the field based on status you can protect the transition, call it 'edit fields' and present the fields you want them to edit on that transition screen. Remove them from the Edit(default) screen and only have them on the Create screen if needed and the View screen.  I've some similar things with approvals using a transition just presenting the 'role approval' field for each role on a different transition. 

[Marco Campeotto]

Hi @Joe Pitt,

currently I am using Jira 6.4.14, what do you mean for "role approval"?

we have 3 roles:

- engineers: a - b - c - d - e - f - g - h (8 users)

- reviewers: a - c - d - e - h (5 users)

- administrators: a - b (2 users)

and we have the status situation above.

For each transition there is a specific screen (only reviewers have the permission to do a transit between 2 status) and one of reviewers edit specific fields in screen.

So the transition screens are "manage" by the reviewers, that's why I search a way to "control" the edit permission of particular field. 

For example
In status A, a user edit field "Main"

when a finished to edit "Main", a tag a reviewers

Reviewer decide about the transition (he edits transition screens and assigns the issue to another/the same user, for example a again) 
[here there is an other problem, a user is member of both engineers and reviewers (very common situation), so a has the possibility to move "without" control on workflow and we don't want this]

In status B, a user edits field "Description" but he has the possibility to edit the field "Main" and I would like to prevent this.

[Joe Pitt]

By having users in multiple roles involved in this I don't see a way to implement it without a complicated script.

[Marco Campeotto]

I think so @Joe Pitt, it would not be a problem to write a script if it is necessary, the problem is how to start to write the script, I installed 

Adaptavist ScriptRunner for JIRA Standard Edition - Installed version: 3.1.4

but I didn't find a guide or simply information about "how to start with scriptrunner" and it is really difficult to find the methods to obtain right information in the API jungle.

[Joe Pitt]

@Marco Campeotto I can't help.  Much of my work has been setting up JIRA and teaching admins how to maintain it. Many are not programmers so I don't use scripting at all. If it isn't built into JIRA or in one of the few supported plugins I've used I don't do it. That makes it easier to maintain in the long run.  A lot of times if you step back you can devise a solution that works. You may need to make some changes to the process. Just because you've always done something a certain way doesn't mean it is the most logical way. One option would be for an engineer to assign a reviewer the issue and then you have a transition only the assignee and a user in the 'reviewer' role can execute. Put the field the reviewer needs to update on the transition screen. The filter 'assigned to me' will show the work to be done and no one else can execute the transition.