Working without a simplified workflow - JIRA Tutorial
Working without a simplified workflow is a free tutorial by Dan LeFebvre from JIRA course
Link to this course(Special Discount):
https://www.udemy.com/course/team-wor...
This is the best JIRA Course
Course summary:
Customize JIRA's agile features.
Understand workflows in JIRA better.
Be able to customize JIRA's agile boards.
English [Auto]
In the last video we created a send to q a column using a simplified workflow in this video. We'll look at how to get the same result. If you're not using a simplified workflow and as I mentioned in the last video if you're fine with a simplified workflow and that's what you're using you can skip this video. But if you're not let's get started by first clearing out what we just added in the last video using that simplified workflow. So I'm going to come in and delete this column here and now we want to actually get rid of that status because we're going to recreate it through the process in this video. So the status is still there but let's actually delete that someone to come into my settings over here. Two issues and then if we scroll down over here on the left hand side we will see statuses and the status that we want to get rid of. Is this send to Cuba that we had created. So this is actually still applied in a workflow so we can't actually delete that. So what we need to do is to deactivate that from the workflow. However we can't actually do that because this workflow is still active. So first we need to create a new workflow and then apply that to our project and that will make the current simplified workflow inactive so that we can get rid of it. OK so that'll make more sense as we walk through this I to come into workflows here and let's create a new workflow so add workflow. This will be called. This would be our dev team workflow add this in now. Right now this workflow is currently in active and what we want to do is to make it active on the dev team project but we don't have any of those other statuses in the dev team workflow is currently using. So let's start to add those in and I want to make sure let's open this up in a new tab because I want to make sure that I get the right workflow as someone of the right status is rather someone to view the existing one. So these are the existing statuses that we're using and basically I'm going to add all of these back in except for send to queue a OK. So let's come in and add in our backlog so you can see this status already exists. We're not creating a new status. We're just adding in one that exists and won't allow all statuses to transition to this one. And that's going to allow all of these two to transition all of the different statuses to transition across each other and the backlog is actually the one that is when a new issue is created. It's added into backlog so let's come in here and add that over here. Yep. And this we can actually remove that status because we don't need that anymore because that's not one in the current workflow. We have selected for development so that's another one we can just add those in. We have in progress and again I know I'm moving pretty quickly on here. This is something that I'd mention at the very beginning of this course. This is a high level course so if you're not familiar with workflows and how workflows work in general I would recommend checking out my understanding during course and that's much more kind of introductory level on a lot of the concepts in Jira including workflows so we need done. Now that's the last one that we should need to add in. Let we go. Done add that in and. All right. So we have all of our statuses except for send to KUSA. So I'm going to come in and we need to apply this workflow to the project. So to do that we need to actually take the scheme and apply the workflow to that scheme because oh well let's take a look at this. I'll show you what I mean by that. So let's come into our workflow schemes and we can see currently the dev project. This project is using this scheme and it's using the workflow. It's saying okay any of these type so we can have different issue types using different workflows if we wanted to. And so we could get this to be a lot more complex where we say you know bugs work go through a completely different workflow and so we only want the bug issue type to be able to be assigned to send a Q A for whatever reason we might want to change that. I'm going to keep this a little bit more open and less restrictive and start with that there. So I'm just going to come in and edit this workflow scheme and rather than use this workflow let's add an existing workflow that is the new workflow that we just created all unassigned issues and that is going to overwrite the the workflow that we currently had assigned their Hey.