Disable edit on all issues in current Sprint while an issuetype(Change Request) is in"Closed" status

[Soham Das]

The use case is that when a Change Request(an issuetype) is in "Closed" status ONLY users of a particular user group should  be able to edit or modify links,attachments,issue fields of all Story/Features in that current sprint.

Just changing the workflow property wouldn`t work as when  the Change Request for that Sprint is not in closed all users should be able to edit and modify issues.

Also we have Power Scripts, so using SIL can also be an option if there is a way of achieving this using SIL.

I have tried the below automation rule with "Set entity property" action but it is not disabling the edit permission.

[Tessa Tuteleers]

Hi @Soham Das ,

interesting question!

Unfortunately, the properties you are mentioning are workflow properties, not issue properties, so I do not think you can configure this in that particular way.

Whenever I need to make editing conditional, I usually remove permissions for editing altogether by using the workflow properties you mentionned on the statusses, and use conditional "Any status" -> "Itself" transitions to allow the edits whenever I want (and for whatever fields I want).

If you have apps like Scriptrunner or JSU, you can make the transition conditional to a JQL (e.g. a JQL to check for closed change requests), so users only see the edit transition when they are allowed to.

Hope this helps

• Tessa

[Soham Das]

@Hi @Tessa Tuteleers 

"If you have apps like Scriptrunner or JSU, you can make the transition conditional to a JQL (e.g. a JQL to check for closed change requests), so users only see the edit transition when they are allowed to." -

Actually I do not want to just disable a transition but disable all edit/modification on the issue. I believe you are suggesting the use of workflow condition that will check if CR is closed or not and return true/false to allow a wf transition. 

"Whenever I need to make editing conditional, I usually remove permissions for editing altogether by using the workflow properties you mentionned on the statusses, and use conditional "Any status" -> "Itself" transitions to allow the edits whenever I want (and for whatever fields I want)." - Could you please explain this approach a bit differently? (with an example maybe). I do not get what exactly we are trying to do here.

Thanks

[Tessa Tuteleers]

Hi @Soham Das ,

you can look at it like this: an issue has 3 screens, 1 for creating the issue, 1 for editing the issue, and 1 for viewing this issue.

Now if you were to add the editing issue screen as a transition screen, do you agree it would be as if you were editing the issue?

So, if we were to disable editing the issue itself altogether (with status properties), and implement said transition, then a user would only be able to edit the issue while using that transition, right?

In that way you can be way more specific about who can edit what by using transitions as a means of editing, and putting conditions on those transitions.

If you condition has nothing to do with the process (workflow) of that issue, but with external factors (like yours), you can add a specific any status -> itself transition, so you don't need to mess with your statuses to be able to do this.

It would look like this:

Good luck!

• Tessa