GitHub Issues and Projects Tutorial: Work Items, Fields and Planning Views

Issues describe work and discussion, while Projects organizes items through fields and views. This tutorial connects those planning mechanisms without confusing them with source-control events. You will examine status definitions, item relationships and links to relevant changes. A board can show intended progress, but its labels are useful only when the team understands what evidence supports each state. Planning remains a model of work rather than an automatic reflection of every code operation.

Here's a popular GitHub Issues and Projects video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use GitHub Issues and Projects Tutorial: Work Items, Fields and Planning Views

Frequently Asked Questions

Is a project field the same as an issue's open state?

Project fields organize items according to the project's planning model, while an issue has its own lifecycle state. They can be related but are not inherently identical. Interpret each according to the workflow that maintains it.

Does moving an item to Done merge its code?

Moving an item changes planning information. Source integration and deployment are separate operations unless explicit automation connects them. Check implementation evidence before assuming a board position means the target branch or live service contains the work.

Why define status meanings explicitly?

A label such as Ready or Done can represent different conditions to different people. A shared definition makes planning information interpretable. It should identify the evidence required rather than rely on the label's apparent meaning.

What does a filtered view provide?

A view presents items according to selected fields and filters, helping answer a planning question. It does not create another independent copy of the underlying work. Understand the filter when an expected task appears absent from that view.

How should issues be connected to development?

Link the relevant proposal or commits and explain how they address the issue. That relationship supplies implementation context. Issue discussion alone does not establish that the requested behavior has been implemented, reviewed or published.