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

How to check if the default value is updated

rbalamu2

Hi Team,
I have a field named "Analysis Notes" and have a default value as below
Cause of the defect:
Root cause of the defect:
Impacted area:

When a user moves the status of the issue from "Review" to "Implemented" I want the user to fill in the value of "Analysis Notes"

I have created a screen as "Analysis screen" and added the field "Analysis Notes" to this screen.

The problem is that, since it has the default value my validator condition to change the "Analysis Notes" is not working.

Please give me a solution.

Accepted answers

John Funk

Hi @rbalamu2 - Are you using any add-ons like JMWE or ScriptRunner?

If not, one thing you could do is create a custom field that is hidden (i.e. not on a screen). Then create an automation rule that sets the value of the custom field when the Analysis Notes field is update.

Then you can base your validator on the value of the custom field.

I would just use a radio button type with No and Yes for the custom field. Set the value to Yes when the field is updated. Then set your validator to say the custom field must be equal to Yes.

All comments

John Funk

Hi @rbalamu2 - Are you using any add-ons like JMWE or ScriptRunner?

Then you can base your validator on the value of the custom field.

I would just use a radio button type with No and Yes for the custom field. Set the value to Yes when the field is updated. Then set your validator to say the custom field must be equal to Yes.

Craig Nodwell_7eve9b

Hi @rbalamu2 do you have any plugins available to you? This would be a perfect example of the need for a screen behavior, a feature of Scriptrunner. Short of that all I can suggest to you is to remove the default value, or test in your condition that the value of the field is both not null and also that the value of the field is not equal to your default value (reflecting edits to that default value).

rbalamu2

Great @John Funk

rbalamu2

Awesome. Thanks @Craig Nodwell

rbalamu2

Hi @Craig Nodwell ,
I am using Issue fields condition, from automation to set the condition.
I have the below default value:

*Cause of the defect:*
*Root cause of the defect:*
*Impacted area:*

Since it has space between each line, it is not considering the condition which in turn doesn't validate the field. Kindly help!

rbalamu2

Hi @John Funk ,

I am using Issue fields condition, from automation to set the condition.
I have the below default value:

*Cause of the defect:*
*Root cause of the defect:*
*Impacted area:*

Since it has space between each line, it is not considering the condition which in turn doesn't validate the field. Kindly help!

John Funk

I have not tried this before, but try this syntax to remove the extra lines between

{{issue.summary.replaceAll("\n", "")}} to remove all newline characters ("\n") instead of {{issue.summary}}.

abhishek.s-j

Hi @rbalamu2 ,

Add this validator:

"Fields required or changed (by JWT)"

and then choose as below, when prompted:

validation as "must be changed"

This should resolve the problem you were facing, let me know if it does not ?

Also, @John Funk and @Craig Nodwell , is this approach right, I wanted to check with you community leaders, if this fixes the issue.

Hope it does !

Thanks,
--Abhishek

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud