Introduction to Workflow - Create JIRA Workflow from Scratch

Manish Verma
A free video tutorial from Manish Verma
Test Manager, Trainer, Blogger - www.rcvacademy.com
4.2 instructor rating • 7 courses • 36,499 students

Lecture description

In this JIRA workflow tutorial you will learn how to create JIRA workflow from scratch and add status and transitions.

Learn more from the full course

Workflows in Atlassian JIRA

Learn Atlassian JIRA Workflows in detail and understand advanced workflow concepts

01:25:29 of on-demand video • Updated

  • Learn about JIRA workflow advanced concepts
  • Create JIRA Workflow from Scratch
  • Learn how to edit a JIRA Workflow
  • Learn about JIRA Workflow Triggers
  • Learn about JIRA Workflow Conditions
  • Learn about JIRA Workflow Validators
  • Learn about JIRA Workflow Post-Functions
  • Learn about JIRA Workflow Schemes and Associate workflow to Scheme
  • Learn how to configure JIRA board and Map workflow status to JIRA
English [Auto] Hello guys. Welcome to Dera workflow tutorial. In this tutorial series I'll deep dive into the general workflow and we'll start creating gyro workflow from scratch and then understand all the details in the durable flow and how you can utilize the gyro workflow customization. As per the need in your project. So let's get started. So I'm here logged in as the Jira administrator and what I'll do is I'll go back to the do the admin section click on the right call green and click on issues now it will ask you to re-enter the password admin passport. And here I am in the issued section of the administration and below that you'll see the workflows. Now what exactly is a workflow in general. So in a data is a sort of a tool or agile software development tool wherein you can manage your different agile development methodologies like scrum command etc. Now all the issues in or any sort of any project in 0 is a collection of issues and then how those issues are transitioning from one state to another or from start to finish is basically the timeline by the workflow and workflows underlining sort of flow that is followed by each of the issue within Jira and there are some default issue types and then you can also create a custom issue types and custom Workflows as per the need for the project. Now if we see the workflows in the data and I'll give you a brief about how the workflow will look like so this is the workflow that I created recently. If you just click on view this workflow it will give you detail what exactly the workflow looks like. So you have certain state statuses and then you have some transitions are like for example from open to resolved is resolved we should transition then these are the state statuses right to click on edit this particular workflow you will see that you will be able to add a new statuses and then add a transition partial the transition label so these are the labels that are the transition labels. Now this is how the workflow looks like not to create a workflow from scratch is possible through the workflow section if you're logged into the new administration portal and if you click on Add workflow you can provide the name here. So I would say see the Jira workflow tutorial. And just to save time I'll put the same in description and click on and now you can see it will create a blank canvas for you with just an open state to create a workflow right now depending on what exactly you're looking for in your book or how the issue might transition in your project. You will come up with the statuses and the transitions that are allowed from a particular status to the next status. So for this tutorial what I'll do is I'll create a simple workflow. The software development workflow with certain states. So for example open. And then in progress or in development and in testing. So there be a couple of statuses. So let's add a couple of statuses there. So what I'll do is I'll add a new start as they're in development and these statuses will basically need to be categorized into three main categories indeed I sought to do in progress and done so in development. If something is pegged or some stories in development at meetings in progress will change that and create that right. So we have created a new status which is in development. Now there is no transition at the moment. So that's why you see this. These are a red dot now will add another status. So once the development has been finished we'll see it move to interesting and once the testing has been done it will be closed or done state. So my story will be moved to one state. And now here you can see that I have four different states here right. And then what we need to do is we need to add the transition so basically there is no transition so that means you won't be able to move from one state to another. So we have to add the transition from open to development and then just give the name of the transition writes. Click on add. And now you can see that they show there is a transition. Li from open to in development at this arrow is just one sided arrow. That means you can move a transition you can move an issue from open to development but not from in development back to open. If you want to do that you have to add an under transition and say from in development to open and then you can say name is open and it will allow you to move issue from open to development and then from in development back to open. Now there is another thing to notice here in workflows is if you click on Add transition and sorry if you click on any of the statuses and click on close to all status to transition to this one that means it doesn't matter which status a particular issue is it will be able to directly transition from open to interesting or in development to testing or done to test. So usually that is if you're using software simplified workflow that is okay but most of the time it's not what the project needs TAA. They'll be mostly days. Taxes are at the transition between their statuses will be sort of really controlled in a way that which issues can transition from what status to what status so we'll add another transition and finalize this works workflows in development to in testing and testing. And again from interesting as the name right. So that's a simple very simple workflow. And what this workflow state is that you can move from open to in development and from in development back to open. And then you can also move from in development to testing but you can move from back from testing to in development and then from testing you can move to complete. Now what will happen in this sort of scenario is that if your issue is in testing at the moment then you can move it back. You can only move it to one state and then once it is done you can't even reopen the issue because there is no transition back to open. So it's a good idea to add a status has reopened because there might be possibility when your testing fails and you might be required to reopening an issue right. Or even from the down state you might be required to reopen an issue and then add to transition from testing to reopen. Right. So if you're simply the other way to either transition if you simply click on a status and then drag and drop the arrow to the state then it will automatically add the transmission of contagious testing famed and that case they should be reopened. I could see this transition coming here then from done it's up to you if you want to add but from testing you can reopen. And then from reopen you can just keep it and reopen. Are you can you not like again moving back to open. That's totally up to you. So this workflow all these requirements in the workflow come from the project and the people working in the project. So you will get a complete detailed requirement how you have to structure your workflow how you have to create your workflow and what are transitions need to be there in the workflow. Right. So it's not that you will be just alone all alone defining the workflow will be completely based on the system are the project needs and the stakeholders how they need to define this particular workflow. So that's pretty much all about for this tutorial. They'll dig more deeper into the workflows in the next story. Thank you for watching.