Ensuring custom field is populated before adding user story to sprint

[ori gal]

Ensuring custom field is populated before adding user story to sprint

---

Hello,

I am currently using a custom field in our User Stories that needs to be populated when adding the ticket to a sprint. The value of the field is not important, but it must not be empty.

Making this field mandatory during ticket creation is not a viable option, as it is typically set during sprint planning.

I considered adding this as a condition in the workflow transition from "Feature request" to "To do". However, the "Value Field" condition does not support simply checking if the field is populated without specifying the actual field value.

Do you have any suggestions on how to ensure this field is filled before the ticket is added to a sprint?

Thank you!

[Maciej Dudziak _Forgappify_ · Accepted solution]

Hi @ori gal

Instead of condition, consider using validator, which also restricts transition. There is a Field Required Validator out of the box in Jira

Cheers

[ori gal]

You are 100% correct. it worked great. thank you!

[Vicente Domínguez _Decadis AG_]

Hello @ori gal,

I am part of the Decadis team and it might be possible to validate if the field is filled with the Jira expression validator of JWT for Jira Cloud in a given transition.

If you are interested in our app, could you specify the type of field that you would like to validate? If it is a custom field, we have some examples in the use case Evaluate custom fields.

Please, feel free to contact us at any time via our support portal.

Best regards,

Vicente

[ori gal]

Hi @Vicente Domínguez _Decadis AG_ , thank you for your reply.

Im intrested to resolve this using Jira's capabilites. we are a very early stage startup witn a limited budjet, and cant effort additional expances.

Thanks,

Ori