"Field Required Validator" of Atlassian not showing red Asterix

[Fabian Duft]

Hi,

I am facing a problem with Jira Cloud.
I have a project with custom fields, that are required on certain transitions, but should not be required all the time. I can't set them as "required" in the field configuration)

Therefore I am normally using the Field "Required Validator" of JSU on a transition in Jira (Server) 
As Jira Cloud offers this functionality I am using their Field Required Validator. This works by telling a user that a certain field is required, if it is not filled with content, but doens't show the red asterix as an indicator, that these fields are required.

Can someone explain to me why this is not working?

[Fabian Duft · Accepted solution]

The provided Field Required Validator in Jira Cloud unfortunately does not support the red Asterix.

The solution that workes best for me is adding a description to the field description of the issue type.
By adding a red "(required)" statement at the top of the description.

Description:
{color:red} (required) {color}
The rest of your description.

[Oliver Siebenmarck _Polymetis Apps_]

Hi @Fabian Duft ,

To get the red asterisk, you need to make the field itself required – which would make it required all the time, as you already know.

I am not aware of any other way to get the red asterisk displayed; I am pretty sure that it does not work with a validator (unfortunately).

Personally, my workaround is to always use a transition screen when introducing a required field in a transition. This way, the feedback for the user is much more immediate than without, albeit still much slower than just having the direct visual info.

Hope that helps,
  Oliver

[Fabian Duft]

Hi @Oliver Siebenmarck _Polymetis Apps_ ,

Thank you for your response.
I am trying to change behavior with the introduction of required fields as well.

Setting the description of a field in the field configuration with wiki markup:

{color:red} (required) 
                  Description
{color}

is also quite sufficient :)

Cheers,
Fabian

[Oliver Siebenmarck _Polymetis Apps_]

That's a pretty good idea, thanks!

[Denise_Wuethrich_beecom_products]

Hi, @Fabian Duft The Required Fields Validator of Jira Cloud is under Jira’s control, not JSU, unlike in Server and Data Center. Might be best to open a Jira ticket for this issue.

[Kelley Cooper]

Hi @Fabian Duft ,

Recently, we discovered you can require a value in a specific field AND display the required field indicator (the red *) on a workflow transition screen using a ScriptRunner Behavior. When it worked it was like the heavens opening and cash raining down! :)

With a Behavior you can:

• call for the Comment field to be required (thereby displaying the required field indicator*) 
• based on a condition being met, and the condition can be a specific workflow action (read specific transition) in a specific workflow 

In the Behavior you can

• map the Behavior to different projects and issue types
• add the field you want to make required to the Behavior
• configure whether you want the field to be optional/required, read only/writable or shown/hidden
• add a condition to the field where you will configure Applicability (in this case, you'd use When (Behavior will happen if condition is true))
• set Condition = Workflow Action
• in Guide workflow select the workflow containing the transition for which you want to make the field required (note the list of workflows in this list are driven by your project/issue type mappings for the Behavior)
• in Workflow Action select the transition where the selected field should be required

Even better, once you create this Behavior you can reuse it as many times and in as many different Jira projects as you by simply adding more mappings in the Behavior to more project/issue type combinations.

You can find more the details in the Field Required on Transition example in the ScriptRunner for Server/Data Center documentation.

[Joe Pitt]

JSU has always worked that way. Aside from comments I don't put any field on the transition screen that isn't required. In my Using JIRA document I give to new users I cover that. 

[Fabian Duft]

What do you mean by JSU has always worked that way?
This does not really answer my question.
I do not understand why the red Asterix is not added in the Cloud version of Jira but in the Server version it does work.

[Joe Pitt]

I've been using JSU since 2007 on server. If it is working in server now it must have been put in a newer release than what I was using last. But it has never worked before and that was a common complaint. Cloud is apparently different. 

[Fabian Duft]

This is possible, I am working with JSU for 6 months now.
Maybe @Denise_Wuethrich_beecom_products is right and I should open a Jira ticket.