...
In both of these projects, you create issues. This is not a mammoth task. You should very quickly recognise that creating issues in Jira is very straightforward once the project has been set up.
There are
...
Create a Kanban Team Manage Project
| Info |
|---|
In this lab you will create a Team Managed Kanban board and populate it with a few issues |
Navigate to https://celestial.atlassian.net/jira/ and log in using your team IDs
Select Kanban
On the next page select team-managed project
In the Name field enter the project name according to the naming convention above - as you are typing you may see project names coming up, do not select them. You are using a single Jira instance, and it retains the names of previously created projects. Let Jira enter the value into the key field, do not edit this field. Also set the access level if it is being shown
Once the project is created you will see an empty board
Turn on the features Backlog and Issues Navigator
You are now ready to add your issues
Decide on 2 stories you want to work with, add them into your project using the “Create Issue” window. In the Labels field create a new label todoapp but prefix it with your teams ID e.g. 01-todoapp. Populate the other fields as necessary. The stories can be found here
An issue can be created by selecting the Create button
Now populate the fields as necessary (no real
Move the issues from the backlog to the board
Move the issues around the board either by dragging them between the board columns
Move the issues around the board by changing the status of the issue (click on the issue the see the following window)
Create a Kanban Company Managed Project
| Info |
|---|
In this lab you will create a Company Managed Kanban board and populate it with a few issues |
Navigate to https://celestial.atlassian.net/jira/ and log in using your team IDs
Select Scrum
Select Company managed
In the Name field enter the project name according to the naming convention above - as you are typing you may see project names coming up, do not select them. You are using a single Jira instance, and it retains the names of previously created projects. Let Jira enter the value into the key field, do not edit this field. Make sure the two checkboxes shown here are deselected. Once you’ve entered the project name the Create Project button will be highlighted, select it
Once the project is created you will see an empty board.
If the backlog is not showing turn the feature on
You are now ready to add your stories
Decide on 2 stories you want to work with, add them into your project using the “Create Issue” window. In the Labels field create a new label todoapp but prefix it with your teams ID e.g. 01-todoapp. Populate the other fields as necessary. The stories can be found here
An issue can be created by selecting the Create button
Now populate the fields as necessary
Move the issues from the backlog to the board
Move the issues around the board either by dragging them between the board columns
Move the issues around the board either by changing the status of the issue (click on the issue the see the following window)
Working with Issues
| Info |
|---|
In this lab you will reuse the the Kanban Company Managed project, create an additional board, and populate the two boards with different types of issues |
Make sure you are in your TODO App (KB CM) - so this is the Kanban Company Managed Project
If the project is not current, select the project from the Projects dropdown menu
On the left side below the project name you should see the word “Planning”, you will see a dropdown button, select it, it will show the current board in the project and other boards belonging to other projects. At the bottom is an option to create another board, select it
You will now have the option to create either a Scrum or Kanban board
Select Kanban, on the next screen select “Board from an existing project”, then select Next
Populate the board as shown here
Prefix the board name with what you intend to populate the board with (in this case - Tasks), then your team ID, and lastly the project name.
Select the project that will own this board. This should be the project you are currently in. Finally, select “Create board”
Select the view to show all the boards, you should now see your two boards
Select the original board that was created with the project. we are going to rename it so we know exactly what type of Issues will appear on it. Select the three dots on the upper right side of the board
Select board settings, then General
Select the Board name, edit it and prefix the name with (Stories)
Select “Back to board” upper right of the screen. It may take up to a minute for the board info to update (refresh the browser if you don’t see the changes), but once it does select the view to show all the board and it should look something like this
Review the sections “WORKING WITH ISSUES” and “ORGANISING YOUR BOARDS” in the PDF
Select one of your stories and break it down into smaller sub-tasks
Select the story on the Kanban board
A new window appears detailing the story, select “Create subtask”
A new section appears allowing you to enter to Subtasks summary title, enter a title and select “Create”
Create two sub-tasks
Close the window and navaigate to the Sub-tasks board. You will see that all the Issues are visible
We need to edit the filter for the board so that it only shows the Sub-Tasks and not the stories
Goto to the board’s settings (upper right of screen, the 3 dots), look for the “Filter Query” field - this will take you away form the project to an area dedicated to filters and issues
Edit the query by adding the following query element (add Tasks and All Sub-Task) - whilst you are editing the query switch between the JQLand Basic view
Once completed click the Save link at the top of the view
Select Projects and your project to see the changes (you may need to select the board to see if filter has been applied correctly), it should llok like this
Select the Story board. If it shows more than stories, edit its filter
After editing it, it should look like this
Navigate back to the Sub-Tasks board
Move each Sub-task to the done column
When the last Sub-task has been moved, you should be prompted with a request to update the parent Story, select update
Navigate back to the Storyboard. You should see that the Story that owns the two Sub-tasks has been moved to the done column on the storyboard
Working with Workflows
The easiest way to work with workflows, is to copy an already active one, modify it, and then assign it to a board
The three steps can be summaries here
Using (Global)Issues/Workflows, find the project and copy the workflow. Once copied it will sit under Inatactive workflows
In the project, go to project settings/workflow, Add Workflow, Remove the old workflow
Publish the change
Steps with a little more detail
...
Go to Jira global settings and select Issues
...
Now select Workflows
...
Locate your project and select the settings option (far right three dots)
...
Select Copy, to copy the workflow. Give your new workflow a new unique name that will identify you and the board
...
Modify your workflow according to how you see it working. In this example, we will remove the All transitions of all states except the one going into the BACKLOG. Jira automatically saves every change
...
So the new workflow will look something like this
...
When you have finished, select the Workflows option on the right hand side. and then click on “Inactive Workflows”, your new workflow should be listed
...
If you want to check if the workflow is correct and was saved, select the options menu (3 dots to the right of the workflow) and Edit
...
Select your project from the Projects menu
...
Select the board you want to apply the workflow to
...
Select Project settings / Workflows / Add workflow / Add Existing
...
Locate your workflow
...
Select the issue types this workflow will affect, then select Finish
...
Finally, back on the Workflows page select Publish
...
Confirm that you want to associate this workflow with the board
...
Wait for the global change to complete then select Acknowledge
...
six labs. Follow the sequence to get the best out of the labs
Part I - Team Managed Kanban Project
Part II - Company Managed Kanban Project