Required Fields - Existing issues

Jerry O'Sullivan
Contributor
May 11, 2021

Hi

We have made some fields required for our bug tickets...This works fine for the new tickets

Existing tickets seem to ignore this, is there anyway to enforce this on legacy tickets so when they are editing the fields are required

Thanks

J

1 answer

1 accepted

0 votes
Answer accepted
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.
May 11, 2021

Hi Jerry - Welcome to the Atlassian Community!

You could add a validator to each transition to require those fields. That way they can't move the card without the fields being field in. 

Jerry O'Sullivan
Contributor
May 11, 2021

Thanks @John Funk  I was looking at that...but I want it only for a specific issue type - bug - Can I set up a validator for this? Would I need a separate workflow for bugs :(

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.
May 11, 2021

Yes, you would need a separate workflow for Bugs - OR - you can use an add-on like JMWE where you can do conditional validators.   :-)

You could just copy the existing workflow and label it as the Bug workflow and then modify that. So the process is pretty quick and easy. 

Jerry O'Sullivan
Contributor
May 11, 2021

Thanks @John Funk . I didn't want the overhead of an additional workflow but it looks like it might be the only no cost option 


Thanks for the prompt response!

Like John Funk likes this

Suggest an answer

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

Atlassian Community Events