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; } } }

ScriptRunner: Prevent Edit Issue Screen from accepting the user input based on specified conditions

unknown

Hey everyone

I currently have a behaviour which sets the assignee as required on the Create Issue Screen if a certain issue security has been selected. In addition to that, a workflow validator prevents the user from creating the issue if an assignee has not been set.

The behaviour works on the Edit Issue Screen as well. Since this action is not part of a workflow however, the user could set the appropriate issue security, leave the assignee on unassigned and it would be accepted like that. The problem now is, the team of assignable users is then unable to view the issue.

I then tried to create a custom listener for the Issue Updated event and display a error message if that would be the case. Since this listener gets activated AFTER the issue has been updated, it only displays the message but does not prevent the faulty input.

Any ideas on how I could achieve my desired behaviour?

Thanks and BR

Marius

Accepted answers

All comments

Jenna Davis

Hello,

Just so I'm understanding the problem, you have a behaviour that makes the assignee field required if a certain security field is set. I'm not really seeing why you need a validator/listener if the field is getting set to required, the issue should not be allowed to be Created/Edited if you have a required field left blank.

If I'm understanding the problem incorrectly, please let me know. I think you might be able to find simple solution for this though.

Could you please send me your behaviour's code and tell me how you're setting the behaviour up?

Regards,

Jenna

unknown

Hi Jenna,

Here's my behaviour code.

import com.atlassian.jira.component.ComponentAccessor
import com.onresolve.jira.groovy.user.FieldBehaviours
import groovy.transform.BaseScript
 
@BaseScript FieldBehaviours fieldBehaviours
def childField = getFieldById("assignee")
def parentField = getFieldById(getFieldChanged())
def selectedOption = parentField.getValue()
 
/*import org.apache.log4j.Level
log.setLevel(Level.DEBUG)
log.debug("--------------------This is to test Behaviours Logging----------------")*/

def issueSecurityLevelManager = ComponentAccessor.getIssueSecurityLevelManager()
 
def level = issueSecurityLevelManager.getIssueSecurityLevelsByName("Autor, Bearbeiter & Beobachter")
 
if (selectedOption && level) {
    if(selectedOption == level[0].id?.toString())
    {
        childField.setRequired(true)
    }
    else
    {
        childField.setRequired(false)
    }
}

Yes, you understood it correctly. I think the problem is, that the assignee field is never truly empty. It's either set to a specific user, unassigned or automatic. This is why I needed a workflow validator. See below.

if (issue.getSecurityLevelId() == 10305 || issue.getSecurityLevelId() == 10308)
{
    return issue.assignee != null
}

else
{
    return true
}

The behaviour is set to all projects and all issue types.

Thanks for your help and best regards.

Marius

Jenna Davis

You can check for an 'empty' or null assignee field using something like this in your behaviour:

if (!childField.value) {
    childField.setError("You must set an assignee.")
}

Checking for automatic is a bit more complicated. Do you have your issues set to automatically assign to someone? Or do they remain unassigned upon creation?

Jenna Davis

You could add a simple scripted validator that simply checks for a null assignee as such:

issue.assignee != null

If the issue is set to "unassigned" automatically.

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

addon-com.onresolve.jira.groovy.groovyrunner

groovy