Section 1: What is JIRA
27. Projects keep your work organized
What is JIRA
- Gojira – Godzilla
- Started as a bug tracking. ticket issuing system
- Agile management tool for SCRUM and (Comment?)
- Uses Networked Helpdesk API
28. Creating an account with Atlassian
- https://www.udemy.com/course/devops-fundamentals-tools-technologies-and-infrastructure/learn/lecture/15418628#overview
- https://www.atlassian.com/try
- https://thomasroberts.atlassian.net/
29. Project creating and management
30. Schemes, screens, workflows and permissions
Schemes
Screens
- Select the required visible fields.
- If a field is removed, it can be re-added.
Workflows
- Allow you to see how a status can affect another status
Permissions
Notifications
Section 2: Managing all those work items
31. Epics, stories, bugs and tasks
Epics
- Large stories with a distinct start, end and span multiple sprints
- Are not groups of work items
- Use components and labels instead
- May contain stories, bugs and tasks
- Epics ARE groupings of these!
- Stories, bugs and tasks are all the same level hierachically in JIRA and may be prioritized against one another in a backlog
Stories
- Represents a piece of new functionality
- aka User Stories
- This focuses on the Users
- Format: As a [user] I would like [enhancement] so that I can [benefit realized].
- This is NOT efficient in Jira since the end will get truncated due to limited desktop space.
- Should be completed within a sprint
Bugs
- Something that is broken and needs to be fixed.
- Defects or Problems that should be prioritized against new items.
Tasks
- Something that needs to be done
- Multiple people working on a story or bug
Versions (Not included in this video)
- Releases. Release may include multiple Epics
- Versions are a good way to track an amount of work that has been completed.
Demo
3:45
32. Issue type attributes, adding and removing them
Work Item attribute types
(Work Item = Stories, bugs and tasks)
- Assignee
- Attachment
- Comment
- Component(s)
- Groupings, a way to group items together
- Description
- Epic Link
- Fix version(s)
- Issue type (Story, bug or task)
- Labels: Similar to components, but a way to group items across projects.
- Labels can be created on the fly
- Linked issues: A way to create dependencies between different issues
- Something is dependent on, or blocked by, something else
- Priority
- Sprint: Is this work items contained within a Sprint, and if so, which Sprint?
Demo
1:48
33. Managing your backlog
- Create items
- Prioritize items
- Drag and drop them in the list
- Assign items to epics and versions
- Drag and drop them into the Epic or Version
- create and user quick filters
- Separating work that is fully refined and ready for a Sprint
34. Creating and configuring your board
Missing! This is the same as 35: Creating and starting a Sprint
Section 3: Running Your Project in JIRA
35. Creating and starting a Sprint
- Reviewing the backlog interface
- Backlog view allows items to be prioritized
- Backlog refinement to create ready work
- Sprint planning to plan the commitment
- Starting the Spring
Demo
2:10
36. The daily scrum
- How to use JIRA daily as we move through a Sprint
- How to use the board and burndown points or hours
- Burndown @ 4:00
- How to know if the Sprint is on track to meet commitment
Important Scrum questions
- What impediments I have that prevent me from completing my Sprint commitment.
- Am I doing anything that will prevent other squads or team from meeting their commitments?
- Are there any newly discovered dependencies, or ways to resolve dependencies that we found since our last scrum?
37. Smaller stories or tasks
What is the best way for work to be structured?
- One story per person?
- Use sub-tasks to make things more specific
Answer: Which method will get the work done fastest?
- Swarming
- Focus on the team, not the individual
Demo
4:15
38. Closing the sprint – the sprint report
Section 4: Reporting
39. Burndown report
Demo
2:35
Reports > Burndown
40. Sprint report
Sprint reports
Reports > Sprint Report
- Summary of the Sprint
- Shows the burndown
- Shows
- Work completed
- Work not completed
- Work added (notated with an asterisk)
- Work removed
Demo
0:20
41. Velocity chart
- Gray bars represent what was committed (Story points)
- Green bars represent what was completed
- Height of completed bars over time can show if velocity is improving or declining
42. Release and epic burndown
The Release report should give you an idea of Velocity
- An Epic is a container of work
- A large story that would span multiple Sprints
- A Release is a version that has been deployed
- There may be multiple Epics in a Release
43. Version and epic reports
- Version reports provide estimated project completion dates (both optimistic and pessimistic) based on velocities over the course of the version.
Section 5: Searching and Filtering
44. Issue searching using JQL (JIRA Query Language)
- JQL: the most flexible way to search Jira
- Get started with Advanced Search and JQL
- Uses fields, values and keywords, much like SQL
45. Saving and managing filters
Once a query is searched, you can save it. It then becomes a filter that you can select from the Managed Filters.
46. Executing bulk changes
These use filters.
Elipse (…) Bulk change > Select the issues > Follow the wizard to make the changes you wish to make.
47. Creating new boards from saved filters
Section 6: Dashboards and Gadgets
48. Creating and managing dashboards
Multiple layouts
- Single page
- Single, 2 and 3 column
49. Adding gadgets to your dashboard
- Gadgets are widgets.
- Boatloads of gadgets available
- Many more from the Marketplace
- Gadgets exist that help you create your own gadgets.
50. Sharing your dashboard
- Public dashboards