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 to make field mandatory depending on specific label?

Yuval Bar Lev

I what to make some fields mandatory when moving from one status to another(this I know how to do),
but I want them to be mandatory only when certain label exists
How can i do it?

Accepted answers

All comments

Bibek_ikuTeam_

@Yuval Bar Lev

Welcome to the community. I assume you are trying to pull this off using the condition/validator in the workflow?

Could you please share an example of what you mean by "want them to be mandatory only when certain label exists"

Ideally using a screen will help.https://confluence.atlassian.com/jirakb/map-a-screen-to-a-workflow-transition-in-jira-company-managed-projects-720634253.html

-Bibek

Yuval Bar Lev

Hi,

example:

in Bugs, making RCA fields as mandatory when changing their status to 'ready for QA' but only when the bug has labels 'regression' & 'staging'

Yuval Bar Lev

we have a screen pop up when changing the status that present the RCA fields
but we want to make them mandatory

Bibek_ikuTeam_

@Yuval Bar Lev I can only think of your standard bug workflow and include the below suggestion on those. <Testing on sandbox is suggested>

Edit the workflow and select the transition to "Ready for QA".
Add a condition to check if the labels contain "regression" and "staging".
Add validators to ensure the RCA fields are mandatory if the condition is met.
Use a scripted validator for advanced label checks if needed.
Publish the workflow to apply changes.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management