requirements to use transition validators

[Joe Chapman]

Using JSM DC 4.20.

The result I'm looking for is to require that the Resolution field gets populated when an Issue has transitioned from In Progress to Done.

My understanding is that there are two ways to do this

1. Use a 'transition screen' like Jira Service Management Resolve Issue Screen and require the Resolution field on this screen.
2. Use a Validator to verify that the field is not blank or null or that it is a specific value or in a set of values.

My understanding also is that each has limitations. Such as, #1 causes the field to become required and it now shows up in other places like the customer portal/form that reporters fill out (e.g., /jira/servicedesk/customer/portal/x/create/yy) And #2 requires use of Insight Query Language (IQL) and Insight Objects and we have no idea how these work.

Is this correct? Is there a simpler way to do this with JSM DC 4.2?

[Nic Brough -Adaptavist-]

No, that's not right.

But I completely understand how you could have got to these misunderstandings - the Resolution field in Jira works differently to the other fields, and we've recently been taking down a number of wildly inaccurate posts made by ChatGPT 'bots that have been posting dreadful answers like the ones I think you have seen and been mislead by.

1. Yes, right about the screen, but you can not make fields required on-screen
2. A validator checks that a field is filled, but does not do anything about getting the users to enter it

There are three ways to set the resolution, and you don't need to do anything about making it "mandatory"

• Some projects let you put a tick in a board column to say "this column is resolved" (Cloud only though)
• Use a post-function (not a validator) in the workflow to set (and clear) it as status changes
• Just put it on a transition screen.  It will adopt a default setting, and while people can change the value, they can not leave it blank.  This is not quite the same as "mandatory"

A note of caution on the "screen" on - never put resolution on a create or edit screen - your users will be creating resolved issues, or accidentally resolving them just by editing them, which you really don't want.

[Joe Chapman]

heh, actually, I came up with this all on my own based on available documentation and my own experience so far with JSM DC 4.20.

Thanks, I will give this a try and come back to 'accept' this as the answer if it solves my problem.