Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 20 Next »

You or your team will have been assigned a number from 1 to 8.

When logging into Jira use the following user name student<team number>@celestial.co.uk.

Password is eOiLxxc4wNa[

Example - student01@celestial.co.uk

Use the following syntax when naming your projects <team number> <space> TODO App (<board type> <space> <managed by>)

Where

  • Team number in the format 01, 02,… 08

  • <space> is a single space

  • <board type> is KB or SCRUM

  • <managed by> is TM (Team Managed) or CM (Company Managed)

Project Naming Examples - 03 TODO App (KB TM), or 01 TODO App (SCRUM CM)

The PDF recaps on the demos the trainer did two weeks ago.

The project is a simple TODO Application, (open the link in a new TAB) the specification can be found here

You are going to create two projects, a Kanban Team Managed project and Kanban Company Managed project. The purpose of the exercise is to simply recognise the difference between the project types.

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 four labs, do them in this sequence

Part I - Team Managed Kanban Project

Part II - Company Managed Kanban Project

Part III - Working with Issues

Part IV - Workflows

Create a Kanban Team Manage Project

In this lab you will create a Team Managed Kanban board and populate it with a few issues

  1. Navigate to https://celestial.atlassian.net/jira/ and log in using your team IDs

  2. Select Kanban

  3. On the next page select team-managed project

  4. 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

  5. Once the project is created you will see an empty board

  6. Turn on the features Backlog and Issues Navigator

  7. You are now ready to add your issues

  8. 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

  9. An issue can be created by selecting the Create button

  10. Now populate the fields as necessary (no real

  11. Move the issues from the backlog to the board

  12. Move the issues around the board either by dragging them between the board columns

  13. 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

In this lab you will create a Company Managed Kanban board and populate it with a few issues

  1. Navigate to https://celestial.atlassian.net/jira/ and log in using your team IDs

  2. Select Scrum

  3. Select Company managed

  4. 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

  5. Once the project is created you will see an empty board.

  6. If the backlog is not showing turn the feature on

  7. You are now ready to add your stories

  8. 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

  9. An issue can be created by selecting the Create button

  10. Now populate the fields as necessary

  11. Move the issues from the backlog to the board

  12. Move the issues around the board either by dragging them between the board columns

  13. 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

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

  1. Make sure you are in your TODO App (KB CM) - so this is the Kanban Company Managed Project

  2. If the project is not current, select the project from the Projects dropdown menu

  3. 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

  4. You will now have the option to create either a Scrum or Kanban board

  5. Select Kanban, on the next screen select “Board from an existing project”, then select Next

  6. Populate the board as shown here

  7. 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.

  8. Select the project that will own this board. This should be the project you are currently in. Finally, select “Create board”

  9. Select the view to show all the boards, you should now see your two boards

  10. 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

  11. Select board settings, then General

  12. Select the Board name, edit it and prefix the name with (Stories)

  13. 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

  14. Review the sections “WORKING WITH ISSUES” and “ORGANISING YOUR BOARDS” in the PDF

  15. Select one of your stories and break it down into smaller sub-tasks

  16. Select the story on the Kanban board

  17. A new window appears detailing the story, select “Create subtask”

  18. A new section appears allowing you to enter to Subtasks summary title, enter a title and select “Create”

  19. Create two sub-tasks

  20. Close the window and navaigate to the Sub-tasks board. You will see that all the Issues are visible

  21. We need to edit the filter for the board so that it only shows the Sub-Tasks and not the stories

  22. 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

  23. 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

  24. Once completed click the Save link at the top of the view

  25. 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

  26. Select the Story board. If it shows more than stories, edit its filter

  27. After editing it, it should look like this

  28. Navigate back to the Sub-Tasks board

  29. Move each Sub-task to the done column

  30. When the last Sub-task has been moved, you should be prompted with a request to update the parent Story, select update

  31. 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

  1. Using (Global)Issues/Workflows, find the project and copy the workflow. Once copied it will sit under Inatactive workflows

  2. In the project, go to project settings/workflow, Add Workflow, Remove the old workflow

  3. Publish the change

Steps with a little more detail

  1. Go to Jira global settings and select Issues

  2. Now select Workflows

  3. Locate your project and select the settings option (far right three dots)

  4. Select Copy, to copy the workflow. Give your new workflow a new unique name that will identify you and the board

  5. 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

  6. So the new workflow will look something like this

  7. 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

  8. 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

  9. Select your project from the Projects menu

  10. Select the board you want to apply the workflow to

  11. Select Project settings / Workflows / Add workflow / Add Existing

  12. Locate your workflow

  13. Select the issue types this workflow will affect, then select Finish

  14. Finally, back on the Workflows page select Publish

  15. Confirm that you want to associate this workflow with the board

  16. Wait for the global change to complete then select Acknowledge

  17. Go back to your board and refresh the screen. Try moving issues around. They should now be following the rules you created in the workflow

  • No labels