Want to validate fields in Jira

[binay_yadav]

We have a use case that if Sprint is added to any task than Story points field should not be empty, it there any native way that Jira cloud offers to achieve this use case.

[Ravi Sagar _Sparxsys_]

Hi @binay_yadav 

There are no field validators in automation but what you can do is this.

• Check if the sprint values is changed on edit issue
• Check if the story points on the issue are empty
• Add a comment or do something else like send an email to grab attention of the relevant people
• You can also clear the sprint field from the issue but I will be careful doing that because it can be annoying for the user. It is better to just let them know about empty story points.

I hope it helps.

Ravi

[binay_yadav]

Thanks a lot for helping out @Ravi Sagar _Sparxsys_ the solution that you suggested might work but we have multiple projects and we are refraining from creating a multi-project or global automation rule for same.

[Gaurav]

Hello @binay_yadav 

This is something that can be achieved using Automation but would depend on your use case. What would you like to do if the 'Story Points' field is empty? I have created a sample Automation that updates the field if empty.

This can be customised as per your requirements.

Please accept the answer if this helps solve your query else respond and allow others to share input.

[binay_yadav]

Hi @Gaurav thanks a lot for helping me out, I'll like to block the user from adding Sprint if Story points are empty.

[Gaurav]

Hello @binay_yadav , in that case, you can clear the sprint fields and add a comment for the user to update the Story Points.

But as @Ravi Sagar _Sparxsys_ suggested, this can be really annoying for the users.

Though I understand that you are averse of creating multiple automation; but since there are no validators currently available, Automation is the option to go forward.

[Bill Sheboy]

Hi @binay_yadav 

You may want to consider having a conversation with the team to better understand why issues are added to a sprint without sizing (story points).  For example:

• How often does the team refine work prior to sprint planning?  Perhaps that activity is missing, and so the team feels rushed during planning, forgetting to size issues.
• When issues are added during sprint planning, perhaps the team could pause to refine them before adding to the sprint
• When adding issues after a sprint has started, the reminder with automation could help.  And, discussing why issues are adding during the sprint may help the team improve and reduce the frequency of this adding.

Best regards,
Bill