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

How can I force a Required Field on a particular Status Change?

Kevin_1kvuap

Hi, can I please get some assistance with a process I am trying to implement? Basically what I want to do is on Issue Types "Bug" and "QA Bug" when the status is changed to Done a custom field "Bug Cause" is made required.

1. I have created a Custom Field called "Bug Cause" as a Select List (single choice) on Issue Type "Bug"
2. I have made the field Required
3. I have added the Custom Field to the Screen we are using
4. The issue is the field is required on Create and not only when Status changed to "Done"

Can I do this with a Workflow Transition Validator?

Thank you
Kevin

Accepted answers

Kevin_1kvuap

Just some feedback on how I implemented this;
1. I created the Custom Field "Bug Cause" on both our "Scrum Bug Screen" and "Scrum Default Issue Screen"
2. I selected only "Bug" and "QA Bug" Issue Types on the "Default Configuration Scheme" for "Bug Cause"
3. I also only selected the relevant "Project(s)"
4. I left the "Default Value" empty
5. I made it a select list and added various 'Bug Causes' eg. Software, Craft config, API etc.
6. Under "Workflow" I edited our "Software Simplified Workflow" for the relevant "Project" and added a Validator to the Status "Done" step, that "Field Required Validator" "Bug Cause" field must not be empty (Remember to Publish your changes)

All comments

Barnali Putatunda_lza0ju

Yes, Kevin, you can set it in workflow validator.
But I see you mentioned you made the field required. If you made it required in Field Configuration, then it will be always required. Rather, make is required via validator only for specific transition.

Somnath Patil_v3yqje

Hi Kevin,

You can make field required by using workflow validator.

To make field required on a particular transition you can use 'field required validator'.

Kevin_1kvuap

Hi @Barnali Putatunda, thank you for the quick reply. I have removed the 'Required' field on the Screen. On the Workflow I edited the 'Done' Transition by adding a Validator "Field Required Validator", it is behaving as expected. How can I make this behaviour only on Issue Type "QA Bug" (Subtask)? Currently it behaves like this for all Subtasks. (It is working as expected for the Issue Type "Bug" (Base))

Kevin_1kvuap

Thank you for the quick feedback @Somnath Patil please see my reply to Barnali above.

Barnali Putatunda_lza0ju

HI Kevin,

I assume you do not have any 3rd party plugin. In that case to achieve what you want you need to have 2 separate workflows, one for QA Bug & other for other subtask types.

If you have some plugin like Scriptrunner /JSU / JMWE etc. which provides some more opportunity to do more customization (writing own script) to keep the same workflow & still having different behaviours for different issuetype.

But in absence of any app, option is to have separate workflows.

Kevin_1kvuap

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud