Field gets mandatory when added to a sprint

[Joachim Schittenhelm]

Hi,

is it possible to make a custom field mandatory as soon as it is added to a sprint?

We also have the JMWE but I could not figure it out.

I found some old issue, but it's ~5 years old:

https://community.atlassian.com/t5/Jira-questions/How-to-require-fields-before-issue-can-be-added-to-a-sprint/qaq-p/431581

Best regards

Joachim

[Ravi Varma]

Hi @Joachim Schittenhelm ,

Please note that we can enforce this at two places, you need to decide if they are apt for you or not

• The issues displayed in the board are based on the filter. So, you can modify the filter such that only issues that have the fields populated (non-empty) are shown in the board. You can move the issues to the sprint. In this approach, the issues which don't contain values for those fields, will not be shown in the backlog as well. 
• Another place where you can enforce this would be, after adding the ticket to the sprint and while moving it to the next column, this implies a transition. You need to identify the transition for that column change and put a validator.

Hope this helps.

Regards,

Ravi Varma

[Joachim Schittenhelm]

Hi Ravi,

thank you for your quick answer!

Coming back to your suggestions:

1. this would break the complete workflow of our teams as the issues would not be visible at all before the value is entered. (neither in the backlog view nor in the active sprints)
2. A validator for a transition is our fallback option.

I still hope that there is some possibility to make it dependant on entering a sprint value.

Regards

Joachim

[Ravi Varma]

Hi @Joachim Schittenhelm ,

Please note that a custom field being mandatory depends on the Field Configuration Scheme associated with that project's issue type and not at issue level, based on status. 

You can explore JMWE as suggested by @Radhika Vijji _Innovalog_ to check if it suits your use case or the link you shared originally - How-to-require-fields-before-issue-can-be-added-to-a-sprint

You may want to look at Auto-Transition-when-an-Issue-is-Added-to-a-Sprint 

[Joachim Schittenhelm]

Hi Ravi,

thank you for the suggestions. I will check especially the auto-transition!

Regards

Joachim

[Tarun Sapra]

Hello @Joachim Schittenhelm 

You requirement is somewhat tricky to implement, because when an issue is moved from spring backlog into a sprint, then only the sprint field is updated and there is no workflow transition. 

Hence, there no proper integration point to insert field validation, which is easily possible in case the issue undergoes workflow transition.

Both @Radhika Vijji _Innovalog_ & @Ravi Varma have provided good answers, and my suggestion you will be that it's best to have the field validation upton workflow transition when the issue moves from open to in-progress with in the sprint because to come up with an alternate solution you might have to invest lot of time, instead of going for a much simpler solution like transition screen validation. 

Hence's upto you to take the decision based on the trade-offs.

[Radhika Vijji _Innovalog_]

Hi Joachim,

You can do it with JMWE if you are adding an issue to a Sprint through a transition. You need to add the "Field is required validator" to the "Backlog" transition (or the transition through which you are moving the issue to a sprint) and in the validator configuration make the custom field mandatory. Are you trying any other/specific use case?

Hope this helps,

Radhika

[Joachim Schittenhelm]

Hi Radhika,

thanks for the quick answer!

We do not have a specific transition when an issue is added to a sprint. Adding a validator to this transition would be no problem.

We add issues to a sprint by

1. drag&drop in the backlog view of jira. (during sprint planning - seems to me the basic method in jira)
2. entering a sprint manually into the field (issues later added to an existing sprint)

Is there any posibility to make a field mandatory this way?

Regards

Joachim

[Radhika Vijji _Innovalog_]

Unfortunately no. JMWE workflow extensions perform actions over transitions only. Moreover, I think the only way to apply a validation is upon a transition. Even the Behaviors provided by ScriptRunner make a field mandatory depending on other data entered on the issue screen (i.e during issue creation or an issue transition). So maybe the only option is to go for a transition.

Regards,

Radhika