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

Avoid duplication of label field value

Yogesh Mude_qi979c

Team,

We have a requirement like..while creating or updating issue users are providing the values and that values should not be duplicated.

For example: let say there is a label type field and already that field has TEST value for an issue and while creating/updating new issue a user should not add TEST value.

Any suggestions will be appreciated.

Note: It's not like only for Label type field if you have any idea or suggestion to achieve this then also welcome. The main purpose is ..user should be able to add multiple values to that field and the values should not be duplicate.

Accepted answers

All comments

Ismael Jimoh

Hi Yogesh,

Other than restricting who can create labels using scriptrunner behavior plugin or using the component field, there is no way to prevent people from creating other labels that do not match the one you already have.

I will lean more towards the component field because it is clear that the project admin is the only person who can add component.

Cheers

Yogesh Mude_qi979c

Hi @Ismael Jimoh

Thanks for your response.

What im thinking is ..we can do it using a script validator where we can fetch all the values of the field and then check whether the new field value is equal to existing value or not.

if so, then we should throw an error called this value already exist.

What do you think?

Ismael Jimoh

This could be possible but then resource intensive as you will either need to do this from a cron service, or by event listener which means issue update event that I cannot recommend.

This also does not scale because if a label has already been used, how does the script determine which to delete and depending on how many issues you have and how many labels per issue it could mean an issue update takes multiple minutes to be completed.

Hence, though this is possible, I cannot recommend it. Instead as suggested earlier constrain available Labels to those someone created and other users can then select from this when they type.

Yogesh Mude_qi979c

Hi @Ismael Jimoh , Yeah I understood but here the problem is we are using a multiline text field where users need to enter the alphanumeric character which is generated in SAP while creating/updating issue manually, so sometimes users are adding same alphanumeric character which is already added by someone on issue.

So my team manager wants that the user should not add the same value.

How we can restrict this.

Eshwar Palem

Hi Yogesh,

Did you find any solution for this as we are also having the same requirement where we want to restrict the user from creating the ticket with the existing value in an alphanumeric field?

Thanks,

Eshwar.

Yogesh Mude_qi979c

Yes, using the script we did it.

First, you need to fetch the values of the label field and see if the user is entering the same values which are already contained. if so, then set the error saying XXX values already exist or contain with XXX issue key. if not, then allow the user to add it.

Eshwar Palem

Is it possible to do this on the Customer Portal?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

script-listener

jira-server

script

validation