How can I bulk change a list of issues to Read-Only?

[Samantha Bragg]

Hi, 

please can you advise me how to bulk change a list of issues that I have used a search to create to Read-Only?

I have realised late that there should have been a workflow property set to do this as they were closed/ cancelled.

Many thanks in anticipation of your help and assistance.

Sam

[Trudy Claspill]

Hello @Samantha Bragg 

If you want block editing of fields in an issue when it is in a particular status, you can do that by modifying the workflow that affects those issues. This will work for a Classic project. I don't know about Next Gen projects because I don't work with those.

1. Open the Workflow that affects the project/issues.
2. Select the Status where you want issues to become read-only. This will show a pop-up that will include the Properties link.
   
3. Select the Properties link.
4. Add the property jira.issue.editable and set the value to false.
   
5. Click the Add button.
6. Save the workflow.

For all issues to which this workflow applies, the issues in the specified Status will now be read-only. Note that this does not prevent changing the issue from the Status to another Status, and it does not block entering Comments on the issue. It prevents changing fields, like Summary, Description, Components, and so on. This will take effect immediately on all issues in that Status that are subject to the workflow. You may have to modify multiple workflows, if you have different workflows for different types of issues, or different workflows for different Projects.

This works for Classic projects. I don't work with Next Gen projects so I don't know what the process would be there.

If you want only specific closed issues to be read-only vs. the above process for affecting entire groups of closed issues, I'm not sure how to do that. Maybe with Issue Security?

[Samantha Bragg]

Thanks @Trudy Claspill ,

that's a really comprehensive answer that must've taken time to write, this will be useful.

Thanks again.

Sam

[John Funk]

Hey Samantha - we definitely need more information in order to help. What exactly are you trying to do that you can't right now?

[Samantha Bragg]

Hi @John Funk ,

I wanted to close the issues when the Fix Version they are assigned to is released, but reading the previous reply, it is better to do this via issue closure. Thank you for your assistance though.

[Nic Brough -Adaptavist-]

Read-only is not done on an issue level, it's done by project settings - either having a workflow that limits edit rights or by removing the permission from everyone on the project.  Both of those affect all issues.

If you do mean to do it to all issues (let's say in the "closed" status), you don't bulk-edit, you edit the workflow!

[Samantha Bragg]

Thanks @Nic Brough -Adaptavist- , 

I think that is the best answer going forward, but this wasn't thought of in advance, so now I have a list of issues which were not set to read only in the work flow... I think you are right... a transition from Closed to Closed and making sure that issues are set to read only when closed is the best solution,  we had envisaged doing it when the fix version was released, but this should work too.

Thank you for your assistance.

Sam