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

Stop issue creation if open issue contains custom field value

Rob B_jadbuo

Hi, I need help trying to find a way of stopping an issue being created if there is an open issue with a custom field value selected.

Example:

Issue 1 is Open and Custom Field = 123

User tries to create Issue 2 and populates Custom Field with '123'. I want the creation to be blocked/stoppped with maybe an error message?

I have script runner installed if that helps?

Thanks

Accepted answers

JohnsonHoward

Hi Robert,

I would suggest using a ScriptRunner custom validator, see this documentation: https://scriptrunner.adaptavist.com/latest/jira/custom-workflow-functions.html#_validators

You will want to do something like this (untested /example code)

import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.fields.CustomField
import com.opensymphony.workflow.InvalidInputException
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.component.ComponentAccessor

Issue issue = issue
CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()
CustomField customField1 = customFieldManager.getCustomFieldObject("CF1")
def customField1Value = issue.getCustomFieldValue(customField1)
def otherIssue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("TEST-1")
def otherIssueCustomField1Value = otherIssue.getCustomFieldValue(customField1)
if(customField1Value == otherIssueCustomField1Value)  throw new InvalidInputException("Some combination of multiple fields are in error")

Hope this help.

Thanks,

Johnson Howard (Adaptavist)

All comments

JohnsonHoward

Hi Robert,

I would suggest using a ScriptRunner custom validator, see this documentation: https://scriptrunner.adaptavist.com/latest/jira/custom-workflow-functions.html#_validators

You will want to do something like this (untested /example code)

import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.fields.CustomField
import com.opensymphony.workflow.InvalidInputException
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.component.ComponentAccessor

Issue issue = issue
CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()
CustomField customField1 = customFieldManager.getCustomFieldObject("CF1")
def customField1Value = issue.getCustomFieldValue(customField1)
def otherIssue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("TEST-1")
def otherIssueCustomField1Value = otherIssue.getCustomFieldValue(customField1)
if(customField1Value == otherIssueCustomField1Value)  throw new InvalidInputException("Some combination of multiple fields are in error")

Hope this help.

Thanks,

Johnson Howard (Adaptavist)

Rob B_jadbuo

Hi Johnson, hope you are well! Thanks for this and thanks for the tshirts!

Question about the TEST-1 ..... Should that be the issue type?

Rob (UU)

JohnsonHoward

Ah it's that Robert Bromley! Thought I recognised the name. Hope things are all good your end mate.

TEST-1 is the key for the issue that you want to compare the field with.

So where you have said: "Issue 1 is Open and Custom Field = 123"

TEST-1 is the key for that issue.

and

Issue issue = issue

is the Issue 2 in your respect.

Let me know if you need more help

Thanks,

Johnson

Rob B_jadbuo

Mike thinks my way of explaning the requirements is wrong. This is how he thinks it should be.......

'We need the ability to be able to block a user from creating a new issue (Issue type 1) if one or several issues (Issue type 2) are in an open state.

We would need one field within Issue Type 2 to be the validator for the creation of issue type 1.

Example:

Issue type 2 has 3 issues open with the custom field filled with the follow

o 123

o 234

o 345

No user trying to create issue type 1 will now be able to create and issue in which the chosen field contains 123, 234, 345. However any other contents will allow creation?'

Caoimhin Caldwell

Hi Guys,

I am looking for something similar to this, except when creation of the ticket with the same custom field id info is denied, it also transitions the ticket it matched to another status, any help on this would be much appreciated.

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

jira-service-desk

script-listener

adaptavist