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

Could some one please suggest how we can have a validation on EDIT screen using behaviour plugin ?

shrikant maheshwari

Hi All,

I have tried using behaviour and putting my script in the Initialiser and in the server script as well for the corresponding field but the validation does not seems to work.

Requirement -

Based on the Issue type I need to make a custom field mandatory while creating the issue --- Already done

But at the time of Editing the issue and changing the Issue type the corresponding field does not become mandatory or non mandatory on the basis of issue type?

Accepted answers

All comments

Fabio Racobaldo _Catworkx_

Hi @shrikant maheshwari ,

Initializer works when you open the edit/create screen.

If you want that your code works when change a specific field you need to add the same script also for that field. In your scenario, you need to put the same code at Issue Type field level

It should fix you issue.

Ciao,

Fabio

shrikant maheshwari

Hi Fabio,

I have written the same script in both the places already.

But at the time of Editing the Issue if I change the issue type say from task to Bug then the corresponding "Root cause" field does not become mandatory and vice-versa. Please could you go through the script and let me know the changes .

Screenshot 2022-03-24 at 11.40.45.png

Fabio Racobaldo _Catworkx_

Hi @shrikant maheshwari ,

if you need to make field mandatory based on issue type, the best pratice says to use Field Configuration Scheme based on issue type.

Btw, your code should work, I jest tested it in my local environment.

Please could you share the mapping for your behaviour?

shrikant maheshwari

Hi Fabio,

please find the mapping screen shot and the problem is when i am trying to edit an existing Issue and then changing the Issue type to "BUG" then Root cause field is not becoming mandatory its still non mandatory.

Screenshot 2022-03-24 at 12.53.33.png

Fabio Racobaldo _Catworkx_

Hi @shrikant maheshwari ,

that is the problem. You behaviour currently works just for bug. If you need to work for all issue types (mandatory field should depends form all issue types) you need to edit mapping so that it works at project level and for all issue types.

It should fix your issue.

Fabio

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server