nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to require story points only for User Stories during a transition

Dean Del Ponte_18waas

Developers work with multiple Issue Types (bug, task, user story, etc).

While grooming the backlog, once a story has been discussed and is ready for development it is transitioned to the 'Ready for Development' state by selecting it from a drop down.

I would like to require that story points be entered when transitioning a user story (and only a user story) to 'Ready for Development'.

I see how I can do this for all issue types, but I'm not sure how to do it only for user stories.

All help is appreciated

Accepted answers

Ashkan Malekly_4jfgcl

Hii @Dean Del Ponte

If you want to have just one workflow, you can add a parallel transition on workflow and then on one of them defines a condition that issutype = story and your desire validator (story point must be required) and on another transition define a condition like issuetype != story without any validator

All comments

Bill Sheboy

Hi @Dean Del Ponte -- Welcome to the Atlassian Community!

I believe that you can do that using workflow validators. Please see this documentation for more information:

https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html#Advancedworkflowconfiguration-validators

Best regards,

Bill

Dean Del Ponte_18waas

Yes, it's true that I can add a workflow validator requiring story points be entered for all issue types during the transition, but I only want the validator to be required for user stories.

I could create separate workflows for each issue type and create a validator for the User Story issue type, but this would become a maintenance nightmare.

Maybe I'm missing something?

Bill Sheboy

Yes, you would need different workflows by issue type because you want the field to be mandatory (and use the validator) for only one type: user stories. Although in all other things you could make the workflows identical, and so making board configuration easier.

Ashkan Malekly_4jfgcl

Hii @Dean Del Ponte

Dean Del Ponte_18waas

Very innovative approach! I think I may give that a try.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

transition

workflow