How to Use Jira
Jira Software Cloud is a project management tool that allows you to plan, track, and launch projects Jira also has reporting features that allow project managers to view and take action to improve the team's performance in real-time.
The Curriculum Programs team uses the agile workflow features in Jira to manage all production projects. The purpose of Jira is to act as a single source of truth across the team. Jira integrates with other tools that we use at Codecademy frequently like GitHub, Gmail, Google Calendar, Google Drive, and Slack.
You should have received an email invite to the External Content Production Jira board from the project manager. If not, please chack your junk folder. Let's break down how to use the External Content Production Jira board and its agile features of the Jira.
Tickets (or "issues") are the deliverable tickets that move through the kanban board as the project progresses. Tickets represent deliverables moving through the stages of production. Each issue has an epic tag that's used to associate the issue to its course. For example, an issue may have the epic tag of
Introduction to HTML because that is the course the issue is associated with. You may filter the tickets to see those that apply to your production work only.
If you are stuck or need help with something, you should move the issue to the
Blocked column. Tickets also have fields like Google Drive attachments, link inputs, and deadlines that are used by the team to keep the project organized.
You should attach any files and links to Tickets for easy sharing and visibility. You may add GitHub repository to show information about branches, commits, and pull requests on your code. You can also add files to tickets with the Google Drive feature.
Boards are a view of the project's workflow in the most current, or live, state of the project. Based on the workflow and anticipated outcome of the project, you must choose a Jira board style: scrum, kanban, or hybrid. We will be managing course production with a kanban board. Kanban boards manage work by visually displaying work and/or project tasks at various stages of the project or process.
The workflow of the External Content Production board helps all of us update and track the project in real time. We can also find deadlines and files, or flag any Tickets using the board. Check out an explanation of the workflow below:
All Tickets begin in the To Do column. When the Author starts a deliverable, the issue must be moved to the In Progress column.
While the Author is working on a deliverable, the appropriate ticket should be in the In Progress column. When the Author completes the deliverable, they should move the issue to Ready for Review. If the Reviewer moves any issue to In Progress from the In Review column, the Author must revise the deliverable.
All deliverables in the Blocked column are in a critical state (i.e. problems with tooling) until a solution is found. The Project Manager and Reviewer will be notified when Tickets are moved to this column to address the blocker. Please leave a description of your problem on the issue.
Ready for Review
When the Author has completed their deliverable, they must move the issue to Ready for Review. Once the issue is moved, the Reviewer will be notified that this deliverable is ready for review. The Reviewer will move Tickets from this column to In Review once they’ve begun review.
The Reviewer will move the issue to In Review once they get started. After they complete review, they will move the issue back to In Progress if it need revision or move the issue to Done.
Only the Reviewer can move an issue to Done once review is complete. This column means the deliverable has been approved and the Author may move on to the next step in production.