Development field required on transition?

Esteban Halabi
Contributor
March 6, 2024

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!

 

4 answers

1 accepted

0 votes
Answer accepted
Asmath Basha S
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 6, 2024

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.

0 votes
Maciej Dudziak _Forgappify_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 19, 2024

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

0 votes
Baptiste Massey
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 19, 2024

@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 

0 votes
Asmath Basha S
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 7, 2024

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events