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

Required fileds in two screens

Dana Maria M

Hello,

I have a problem related to some required fields.

I have the following situation:

I created a new flow for a new kind of issue - "New Issue". My flow is: Open - Define - Analysis - Solve - Closed.
The screens for my issue are:
create - New Issue Screen Create
edit - New Issue Screen Edit
view - New Issue Screen View
Create and edit screens have the same fields.
1. Open: Create a new issue.
2. Open - Define : Edit every data I want.
3. Define - Analysis: All my fields became not-editable. I use a new screen - Add Analysis Info Screen - on the transition to add new fields and some of them are required but I need to see them in the view screen to.
The "Add Analysis Info Screen" fields:
My Info, text field, is required
Methods, text field
Actions, text field, is required
Link. text field
The "New Issue Screen View" fields = the "New Issue Screen Create/Edit" fields + the "Add Analysis Info Screen" fields
Everything is perfect until I try to add a new issue! I received the red message: My Info: My Info is required.
I don't understand what happens because I haven't these fields in "New Issue Screen Create", the screen I use for create.

Can you help my with a solution?

Thanks in advance!

Dana Maria

Accepted answers

Jean-Théo _Adaptavist_

Hi @Dana Maria M,

Do you use the field configuration to select the required fields? Because that would mean the field that you select as "required" would be required for the create screen, even if it is not displayed in it.

To fix your issue, you should either :

1 - Add the field to the create screen and set a value for it (while creating the issue)

2 - Remove the field as "Required" from the field configuration and add it as a validation in the transition instead

I hope this helps!

Ismael Jimoh

Hi @Dana Maria M ,

In your configuration, you would require to have this field in your create screen as well since they share the same Field configuration scheme.

My suggestion is to add a validator to your Workflow using either scriptrunner or JSU add-on to make the field required via a validator.

This is explained here if you are using JSU.

Scriptrunner would require you writing a script yourself though.

Regards.

All comments

Jean-Théo _Adaptavist_

Hi @Dana Maria M,

To fix your issue, you should either :

1 - Add the field to the create screen and set a value for it (while creating the issue)

2 - Remove the field as "Required" from the field configuration and add it as a validation in the transition instead

I hope this helps!

Ismael Jimoh

Hi @Dana Maria M ,

In your configuration, you would require to have this field in your create screen as well since they share the same Field configuration scheme.

My suggestion is to add a validator to your Workflow using either scriptrunner or JSU add-on to make the field required via a validator.

This is explained here if you are using JSU.

Scriptrunner would require you writing a script yourself though.

Regards.

Dana Maria M

Thank you for your answer!

I used the "Fields Required" option from "Validators" on my transition but I want to have the red star for each required field from "Add Analysis Info Screen".

Dana Maria M

Thank you for your answer!

I used JSU on my transition but I want to have the red star for each required field from "Add Analysis Info Screen".

Ismael Jimoh

For that, I am unsure as the behaviour of having the red icon next to field field is provided from the JIRA source code and if you are using an add-on, the vendor would need to implement a similar behaviour.

For example this add-on Workflow Essentials does just this.

Dana Maria M

Thank you!

Welcome!

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

Quick Links

Find more posts tagged with

jira