nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JMWE Scripted (Groovy) Condition

Jurica Petricevic

Hi Community,

I have a question, can a condition be made that one user cannot close a ticket if there has ever been an assaignee on the ticket?

This would achieve the principle of 4 eyes for security problems in our Workflow. Can anyone help me here?

Best regards

Jurica

Accepted answers

David Fischer

Hi @Jurica Petricevic ,

using JMWE, you could use a Scripted (Groovy) Condition with this script:

issue.getFieldHistory("assignee").size() > 0

This will check if the Assignee field was ever modified (which is equivalent to saying it was assigned to someone at some point)

All comments

Juan Manuel Ibarra

In this case you should have the history of those assigned in this field which is quite complicated. What you could do is have a multiple user type field (It can be hidden from the user) and every time the assign is changed, the user joins that field.

This will then allow you to compare the list of users of the field with the one that

David Fischer

Hi @Jurica Petricevic ,

using JMWE, you could use a Scripted (Groovy) Condition with this script:

issue.getFieldHistory("assignee").size() > 0

This will check if the Assignee field was ever modified (which is equivalent to saying it was assigned to someone at some point)

Jurica Petricevic

Yes, but in our case more users can be exchanged at one ticket. None of them can close the ticket.

No one who was involved in the solution should be able to close the ticket.

Jurica Petricevic

I need 100 new fields in that case because so many users change on one ticket. Also, I'm not sure how to check all 100 and allow someone to close / test the solution.

David Fischer

So what you mean is that you don't want a user to close a ticket if the same user was ever were assigned to the ticket before?

If so, this is the script you want:

!issue.getFieldHistory("assignee")?.find{it.to == currentUser.key}

Jurica Petricevic

Hi David, I'm not sure why but it doesn't work? Is it still Scripted (Groovy) Condition?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server