Issues are changed to "Blocked" each time they are moved

@Alexander Suraphel

This workflow is a part of the Kanban project template. Please refer to the following documentation section for a video that explains each template.

Basically, the allow-moving-ready-to-pull-only rule is an implementation of the Kanban pull system. Instead of simply moving a card to the next stage (e.g., from Develop to Review), you signal that the card is ready to be moved, and the next assignee can move it and start working with it when they are ready. Ready to pull value of the Kanban stage field is a pull signal (card is ready to be pulled to the next work process stage). This approach helps to avoid piling-up of work in one stage, since cards are moved only when the next assignee can take it and start working with it.

Hope this information was helpful!

PERFECT.. this worked.. Thanks!

By turn Off you mean removing from that list?

Hello,

Just click the crosses near the projects name to detach the workflow as shown below:

Hope it helps. 

Nice, thank you.

@Alexander Suraphel

Sure, it is possible. Edit the workflow's action section like this:

 action: (ctx) => {
const issue = ctx.issue;
workflow.check(issue.fields.is(ctx.KanbanState, ctx.KanbanState.ReadyToPull),
workflow.i18n('The issue is not ready to be pulled'));
if (ctx.issue.fields.Stage.name !== "Review"){
issue.fields.KanbanState = ctx.KanbanState.Blocked;}
},

In this case, the Kanban State becomes Blocked when the card is moved to any stage except for the Review.

Anastasia Bartasheva Can you please explain or refer me to a doc why this workflow is useful/implemented? Thanks

Thanks for your reply Alisa Kasyanova

I think I understand the pull system now. YouTrack seems to put every card that is moved to blocked to signal the person dealing with the next column not to pick the card. From my understanding, when testers finishes testing, they change the kanban state to ready to pull so that the person in change of staging column can pull it. What happens when a tester determines the task doesn't solve the issue? 

@Alexander Suraphel
Do you mean what happens if testers want to move the card back to the Review stage? I suppose it is needed to change the Kanban state to Ready to pull and move the card back, while in a case when testers finish working on the card, they should simply change the Kanban state to Ready to pull and leave the card in the Test stage.

Alisa Kasyanova

Yes, that's what I meant. 

The redundant work I feel is when testers move the card back to Review, the Kanban state of the card is automatically changed to Blocked. Who will change the state to Ready to Pull? What do developers do once their task is complete? Change Kanban state to Ready to Pull then move the card to Review and change to Ready to Pull?

@Alexander Suraphel

It depends on your process and how your team agreed to handle such cases when the card should be moved to a previous stage. If you often return cards to previous stages, then it is possible to edit the workflow or to deactivate it at all to avoid redundant work.

Got you Alisa Kasyanova

Is it possible to exclude only the Review column from the workflow so that Kanban state of cards is not automatically changed when they move to that column? 

Thanks Alisa Kasyanova! 

That did it for me. Got me started with workflows too!