Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to add a transition validator for moving task from Backlog to Sprint

Andy Griffiths February 28, 2019

We want to ensure all of our tasks are story pointed, so would like to add a validator on the transition from Backlog -> Sprint

Is this possible?

I don't see any way to set this in a workflow, only between the broader steps (To Do -> In Progress etc)

 

Thanks

1 answer

0 votes
Jack Brickey
Community Champion
February 28, 2019

For sure.

  1. create a new screen that includes the estimation field
  2. edit workflow
  3. Edit the transition from the ‘backlog status’, probably To Do to In Progress, or whatever is your case
  4. add the new screen
  5. add a validation requiring the field
  6. publish the workflow
Andy Griffiths February 28, 2019

Thanks @Jack Brickey but not sure that's quite what I need.

If I do that, then (at least to my understanding), then I require an estimation whenever a task is created (since item in the backlog enter the workflow in the To Do status)

There isn't a transition from Backlog->Sprint per se

 

If I add the validation in the ToDo -> In Progress transition, then sure, I get an estimation at that point, but it misses the fact that that estimate has been entered after the sprint has started, and therefore affects velocity calcs, burndown etc...

Jack Brickey
Community Champion
February 28, 2019

@Andy Griffiths , yep sorry for the confusion I was thinking kanban and not scrum. So assume you are getting a warning that you have un-estimated issues when starting a sprint but you are wanting to block starting, correct? I expect you may be able to achieve w/ an addon; maybe Scriptrunner or Power Scripts but not sure. I will ping other champions to see if they have any thoughts on this.

Andy Griffiths March 4, 2019

@Jack Brickey no problem - if you have any update or further thoughts would love to hear them as this is still a challenge we're facing!

Jack Brickey
Community Champion
March 5, 2019

my only immediate other thoughts is to restrict who can manage sprints. In reality only the scrum master should manage this but having 2-3 users is manageable. It is easier to get a few folks to follow the rules and not ignore the warning.

Suggest an answer

Log in or Sign up to answer