you can do so by clicking on a TRANSITION in your workflow and then choose, for example, VALIDATORS. and choose that only a user with permission to resolve an issue can move it to DONE prnt.sc/ql4kmn . In order for this way to work, make sure you have RESOLUTION defined for your done status and that your PO is the only one with the permission to resolve. HOWEVER, making PO the only person responsible for resolving issue might create a bottleneck and negatively impact self-organization of your team
Hi, I have one query, can you please explain that if we want to move from other statuses as well then how to do it.Like rt now story can be moved from To Do to in progress and then Done, but cannot moved to on hold and Dev Completed etc.And another query is - I want to create Kanban board with in same project in which I have Scrum board as well. And both boards are having specific stories like Scrum board having dev stories and Kanban is for design related stories. So in case of dependency of story from scrum board to kanban board, how can we link scrum board story to kanban based on status. Like if I have one column in kanban with "Blocked" status and same Status will also in Scrum board. in case of dependency I will change the status of dependent story in Scrum board to "Blocked" then it should automatically moved to Kanban but it should appear in Scrum board as well.And Somehow while configuring it my "TO Do" status got disappear from scrum board. Like once all the created stories are in To Do status but once they will move to "In Progress" then I cant make it to "To Do". Please help and
Great tutorial, thanks. Seems the only way to get from Open to To Do is to click "View Workflow" in the detail view to the right of the board when clicking on the issue card. Is that right or have I done something wrong with the setup? Is there any easier way to set status?
Hi, glad you find it helpful. I have created a video reply for you here ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-3D-o3hCGejM.html Let me know if you have more questions
Thank you for the video. It is not clear for me how statuses are changed, when we go through the TDD testing. The subtask is marked Complete and goes to QA? Or POwner looks through them and assigns to QA manager? After that controls statuses and sends whole story for QA?
@@pitch9693 currently we do manual testing (and for up to 6 month plan to continue this way). Later plan to develop and implement automation. Generally my question is the workflow is for user stories, how statuses of subtasks differ, if they do?
@@pavloredko9880 Firstly, I would like to emphasize that Jira workflow is just a reflection of your teams workflow. Before you set up a workflow in JIra your team needs to agree on a workflow that works best for them. I recommend using different workflows for Stories and Subtasks. For teams I work with (where testers are manual and only do UAT) QA does not test subtasks, since subtasks are usually technical assignments created by developers for developers. QA only test a User Story according to: Acceptance Criteria and/or Test Cases they create. In this case, a subtask shall only go through following statuses: TO DO, IN PROGRESS, COMPLETE. They can't be REOPENED, they can't be IN TESTING for there is no such person who test a subtask specifically (this is an important condition).
@@pavloredko9880 Yes, in Project Settings, choose WORKFLOW and you will see ADD WORKFLOW button. You can add as many workflows as you need and pick which issues types for each workflow. You can;t assign same issue type to different workflows
Complete confusion this explanation between transitions and status. Status are a result after an action, and actions are verbs not names as another status. If you name de Transactions as CREATE, TEST, REFACTOR, RE DO etc it will be must simpler to understand. Because what you need is to understand what you need to do to deliver te itens to a specific status...
@@katerinastasik9272 After the build has been completed, that functionality would be QA tested. Once QA has Approved the testing (test cases), then the end users would test, UAT.
