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

Development field required on transition?

Esteban Halabi

Hi Everyone!

I'm trying to get the development field to be required on a transition.

The devs would like to make sure it has a pull request before it can be moved from In Progress to In Review

I've tried using the "field required" validator on the workflow but nothing happens, I can still transition the issue no with no problem.

I understand the Development field is a bit special, so, is this even possible?

Thank you!

Accepted answers

Asmath Basha S

Hi @Esteban Halabi ,

=> First thing If you want to make a mandatory field in the transition screen you need to create a screen and add the fields you want to add in the screen.

=> Then add the Field configuration and Field configuration scheme with the Issue type.

=> In the field configuration you can make the field mandatory then you can achieve this mandatory field.

All comments

Asmath Basha S

Hi @Esteban Halabi ,

=> First thing If you want to make a mandatory field in the transition screen you need to create a screen and add the fields you want to add in the screen.

=> Then add the Field configuration and Field configuration scheme with the Issue type.

=> In the field configuration you can make the field mandatory then you can achieve this mandatory field.

Asmath Basha S

Hi @Esteban Halabi

=> First thing simply add a New screen in Jira.

=> Don't add any field inside that screen, because in default the comment field is added in the screen.

=> Then in the workflow transition screen add the newly added screen in the transition.

=> And click on the Validators in the workflow and select Field Required validator, inside that select Comment or whatever fields you want to add in the Fields Required for transition and give some error message.

=> Finally publish the workflow. Then it will work as you expected.

Baptiste Massey

@Asmath It seems this doesn't work with the development field, as this panel is specific and doesn't show up in the custom fields available

Maciej Dudziak _Forgappify_

Hi @Esteban Halabi @Baptiste Massey

Although the Development field is available in the Field Required validator after typing in its name, it doesn't work. This is because its content is a JSON file, which is never null, at least from what I see after inspecting the content of the issue.

There is a way to inspect the Development field with jira expression-based validators.

I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira app. In the expression editor, when you start typing the name of your field, you will get a suggestion for the ID. You can inspect it with includes method or any other available function that operates on strings to validate the state of the field. For example:

issue.customfield_10000.includes('state=OPEN') ? true : false

I am leaving a link to the documentaton in case you are interested.

I hope it will help.

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

workflow

required-field

field-configuration