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 creation of ticket with same custom field data

Caoimhin Caldwell

Hi Guys,

Hoping you can help me on this one. I am looking for a way to basically meet the following

Users try's to create ticket and fills duplicate data into a custom field which already exists in a separate ticket. Jira denies this ticket creation due to the duplicate field info

The existing ticket with that info transitions automatically to a new status.

Hopefully have explained that clearly, have Scriptrunner and JSU as plugins so can probably be achieved using that although im still sharpening my groovy skills

Regards

Accepted answers

All comments

PD Sheehan

So it sounds like you are attempting the have the values in that custom field unique across all issues in the project. Is that correct?

What type of field if the custom field?

I see several aspects to this requirement

1) Behaviour

When the user fills in the custom field, create a JQL to search for other tickets matching the input. If nothing is found. All is good. If an issue is retrieved, set an error on the field with a link to the existing issue for the user to click on.

From there, the user might need to manually re-open that ticket.

2) Workflow Validator

Like behaviour, but will report the error only after the user attempts to submit. This will never happen from the UI if the behaviour is also setup, but it will catch anyone trying to use the rest api of some other non-standard ui.

What I would not recommend, is to have either the behaviour or the validator trigger a change in the existing issue. Validations should never trigger transactions elsewhere in the system.
Maybe the user just made a typo or other mistake. They may not really want that other issue to be re-opened.

I can help suggest some groovy script for the behaviour and validator if I'm on the right direction and you confirm the type of field (and searcher) that the custom field is.

Caoimhin Caldwell

Hi Peter,

Yes that’s correct . The field in question is type text field (single line) . From above I think you have the requirements spot on. The link wouldn’t be necessary as these tickets are coming in through an RPA bot. As long as the custom field having duplicate data and a ticket being created is stopped that is sufficient. The only thing I might reiterate is the 2nd point where if that happens the original ticket with the data is then moved to a status in workflow ( this is to highlight it needs to be looked at again hence why another ticket is trying to be logged with the same custom field id. It seems tricky to me but hopefully you could help. Really appreciate this

Caoimhin Caldwell

Oh and the custom field search template is free text searcher

Caoimhin Caldwell

@PD Sheehan would you be able to help on this ? Much appreciated

PD Sheehan

As I said, I think triggering the re-open on the original issue seems like a bad idea. Perhaps the user only made a typo in the custom field and I don't think you should automatically re-open the ticket that matched the typo.

A script like this in a behaviour configuration for your project against the unique field's server-side script should get you close:

import com.atlassian.jira.bc.issue.search.SearchService
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.web.bean.PagerFilter
import com.onresolve.jira.groovy.user.FieldBehaviours
import groovy.transform.BaseScript

@BaseScript FieldBehaviours fieldBehaviours

def uniqueFieldName = 'Unique Text Field'

def field = getFieldByName(uniqueFieldName)
field.clearError() //remove any prior errors

def inputValue = field.value as String // the value the user just typed

def jql = """project = $issueContext.projectObject.key and "$uniqueFieldName" like "$inputValue" """

def currentUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def searchService = ComponentAccessor.getComponent(SearchService)
def parseResult = searchService.parseQuery(currentUser, jql)

assert parseResult.valid , "The JQL ($jql) could not be parsed: $parseResult.errors"

if(searchService.searchCount(currentUser, parseResult.query)){
def issue = searchService.search(currentUser, parseResult.query, PagerFilter.unlimitedFilter).results.first()
def issueUrl = "$baseUrl/browse/$issue.key"
    field.setError("""$inputValue has already been used on issue <a href="$issueUrl">$issue.key</a> if more work is needed, access that issue and re-open it.""")
}

Caoimhin Caldwell

Hi Peter,

I found one issue with this , when you click edit on an issue with this now it shows this message and gives the link to the same ticket so there is no way to actually edit and close an issue now . Is there anyway to only have this behaviour happen on the create screen ?

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira

jira-server