Automation Rule

[chathuri kaluthanthri]

Is there a way to configure issues (Story, Bug, Task) in Jira so that a ticket cannot be any other status other than "To Do" if there is no value entered into the Story Points field? For example, in the board workflows, you can set a rule so that a ticket can't be moved by certain people or a ticket can't skip one of the swimlanes. Basically, I am wanting to know if there is a way to do that same type of restriction but it looks at the Story point field to make sure there is a number entered.

[Dirk Ronsmans]

Hi @chathuri kaluthanthri ,

You mention an automation rule but that's not the way to go.

What you need to do is set a condition (or validator) on the outgoing status transitions. A condition will make it so they cannot see any transition until they enter a value or a validator will prompt them when transitioning to another status to enter a value.

If they leave it empty the transition will be blocked.

Imho, the validator seems to cleanest solution.

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-validators-for-company-managed-projects/

[Nic Brough -Adaptavist-]

The validator allows you to tell them why you are blocking the transition, so it's often better than a condition (which just silently stops them seeing or starting the transition)

[Vishwas]

Hey @chathuri kaluthanthri 

Welcome to Atlassian Community !!

We can add condition/validators is workflow transitions to achieve this. Link on how to configure conditions/validators in workflow https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Advancedworkflowconfiguration

In your case you have to add to all transitions where your issues moves from "TO DO" Status to other Status

Steps to add Validator: Workflow --> In Edit Mode --> Validators --> Add Validator --> "Field Required Validator".

The validator will be like this:

Steps to add condition: Workflow --> In Edit Mode --> Conditions --> "Value Field" then add this type of parameters for Story Point.

The condition will be like this:

Hope this helps !

Regards,

Vishwas

[Dirk Ronsmans]

@Vishwas 

great info, just keep in mind that from a user friendlyness a validator is nicer.

A condition will block the user from doing an action but they won't know what they are missing and need to be educated on it.

With a validator they will get a error prompt/a transition screen which is just a cleaner option.

[Vishwas]

Hey @Dirk Ronsmans 

I was about to respond same. Yes Validator would be the best solution as it shows users what is the required field before we do transition.

Let me edit my answer to accommodate validator too.

Regards,

Vishwas

[Vishwas]

Updated answer to show both option to configure validator and conditions