How do you set a field to "Required" after hitting a step later in the workflow?

TD March 11, 2024

Using Jira Service Management, I have a form that has the "Expiration Date" field for people's accounts. This field is not to be set by the submitter. Instead it is to be set later on by the Approving Managers. I don't want the Approving Managers to forget to set this field once it gets to them for approvals.

Using the automated process, or any other process, how do I make the "Expiration Date" field required once the ticket gets to the Approving Managers? I know if I set it before it will halt customers from submitting their account request tickets.

1 answer

1 vote
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2024

Hi Trentin,

You can edit the workflow and place a Validator on the transition to the status you want it to be required for before going to that status. Use the Field Required validator. 

TD April 10, 2024

@John Funk , I am using Jira Service Management Data Center so I am not sure if that changes your suggestion? I go to Validator and the only options I have are "Assets Validators", "Assets Validators (Deprecated)", "Permission Validator", and "User Permission Validator". There is no section for "Field Required Validator".

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

Yes, sorry about that - the Deployment Type above says Cloud. You will probably need a Marketplace App for that like JMWE.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events