GitHub Projects — Vocabulary and Language
Learn the vocabulary of GitHub Projects: views, fields, iterations, and roadmaps.
0 / 25 completed
1 / 25
What is a 'view' in GitHub Projects?
A view in GitHub Projects is a saved perspective — Board (Kanban), Table (spreadsheet), or Roadmap (timeline). Each view can have different filters, groupings, and columns.
2 / 25
What is an 'iteration field' in GitHub Projects?
An iteration field creates time-boxed sprints within the project — e.g., Sprint 1, Sprint 2. Items are assigned to iterations for sprint planning, and GitHub provides iteration-level velocity insights.
3 / 25
What is a 'custom field' in GitHub Projects?
Custom fields let teams add project-specific metadata to issues and PRs — e.g., Priority (High/Medium/Low), Story Points (number), Team (single select). These power grouping, filtering, and reporting.
4 / 25
What is 'project automation' in GitHub Projects?
Project automation uses built-in triggers and GitHub Actions to automatically update item status — e.g., moving an issue to 'Done' when a linked PR is merged, or setting priority when a specific label is applied.
5 / 25
What is the 'roadmap view' in GitHub Projects?
The roadmap view displays project items on a horizontal timeline using date fields (start date, end date or iteration). Teams use it for release planning and stakeholder communication about delivery timelines.
6 / 25
Sarah: 'Hey team, I've created a new GitHub Project called 'Feature X Development'. I've added a task for John to implement the core logic and another for David to write the unit tests. I want to track our progress closely, especially ensuring we're not falling behind on testing. Can someone explain how I can use GitHub Projects to visually monitor the status of these tasks and proactively identify potential roadblocks before they become major issues?'This scenario highlights a common misunderstanding – that GitHub Projects *only* track individual tasks. While you can certainly monitor progress with simple task status updates, the core value comes from visualizing workflow stages (like 'To Do', 'In Progress', 'Review', 'Done') using tools like Kanban boards.
Sarah is asking for a way to proactively manage her project and this option represents the most direct approach to achieving that visual monitoring.7 / 25
Mark: 'I've just created a new PR and added a comment to the title saying 'Needs Review – UI Changes'. I've also set the project field to 'UI/UX' so that the reviewers know what area to focus on. However, the team keeps asking me if I've assigned this task to anyone within GitHub Projects. What's the best way to clarify my intentions and ensure they understand how the project fields are being used?'This question addresses the common misunderstanding that project fields *automatically* assign tasks. While they provide context and categorize work for reviewers – like indicating 'UI/UX' is a priority – they don't replace actual task assignments within the PR itself. The correct answer clarifies this distinction, emphasizing that task assignment should still be set within the PR, alongside the project field information. Options A and C incorrectly assume the team understands the nuances of categorization vs. assignment, while option D misinterprets how project fields function.
8 / 25
Liam is reviewing a pull request for a new API endpoint. He notices the PR description states: 'Implement User Authentication'. The project field associated with this PR in GitHub Projects is set to 'Authentication'. A teammate asks Liam, 'Are you tracking the progress of authentication specifically through this project?' Which of the following best describes Liam's current usage and the intended purpose of setting the project field?
The question highlights a common misunderstanding about GitHub Projects. While project fields *can* be used to track progress on specific features, they are most effectively used at a higher level—to categorize and group related work. Setting the field to 'Authentication' indicates Liam is consciously tracking the progress of that particular feature area within the broader scope of the larger project; it's not simply a way to assign tasks but a way to *monitor* specific functional areas. Option A incorrectly suggests testing is independent of the project field, while options C and D misinterpret the primary function of project fields.
9 / 25
Alex: 'Hey team, I've created a GitHub Project for the 'Nova' redesign. I've added tasks for styling and front-end implementation. To help visualize our progress, I've set the project field to 'Front-End'. However, I'm getting feedback that it's not clear how this relates to the overall Nova project roadmap. Should I be using the project fields to track individual features within the larger redesign effort, or is there a better way to link these tasks to the broader goals?'This question addresses a common misunderstanding of GitHub Projects' purpose. While project fields *can* be used for granular tracking, their primary function is to provide strategic context – linking tasks to broader goals like 'Nova Redesign'. The incorrect options reflect the belief that they're solely for detailed task management or ignoring their strategic role entirely. The correct answer highlights the intended use of project fields as a way to connect individual features within a larger initiative, aligning with the overarching roadmap.
10 / 25
David: 'I've set up this GitHub Project for the 'Phoenix' migration. I've added tasks for database schema changes and data transformation. I'm using the 'Migration' project field to keep everything organized. Emily asks, 'Are you tracking all the individual steps of the migration within this project, or are you seeing it as a larger initiative?'This question tests understanding of how project fields are *intended* to be used. The core principle is that a project field represents an overarching initiative or category, not necessarily granular tasks. Options A and B misinterpret this by suggesting tracking every single step within the project, while option D incorrectly states the opposite – a project field should indeed provide a high-level overview. The correct answer reflects best practice: use the field for the overall migration and link related tasks as needed.
11 / 25
Sarah: 'Hey team, I've created a new GitHub Project called 'Feature X Development'. I've added a task for John to implement the core logic and another for David to write the unit tests. I want to track our progress closely, especially ensuring we're not falling behind on testing. Can someone explain how I can use GitHub Projects to visually monitor the status of these tasks and proactively identify potential roadblocks before they become major issues?'This scenario highlights a common misunderstanding – that GitHub Projects *only* track individual tasks. While you can certainly monitor progress with simple task status updates, the core value comes from visualizing workflow stages (like 'To Do', 'In Progress', 'Review', 'Done') using tools like Kanban boards.
Sarah is asking for a way to proactively manage her project and this option represents the most direct approach to achieving that visual monitoring.12 / 25
Mark: 'I've just created a new PR and added a comment to the title saying 'Needs Review – UI Changes'. I've also set the project field to 'UI/UX' so that the reviewers know what area to focus on. However, the team keeps asking me if I've assigned this task to anyone within GitHub Projects. What's the best way to clarify my intentions and ensure they understand how the project fields are being used?'This question addresses the common misunderstanding that project fields *automatically* assign tasks. While they provide context and categorize work for reviewers – like indicating 'UI/UX' is a priority – they don't replace actual task assignments within the PR itself. The correct answer clarifies this distinction, emphasizing that task assignment should still be set within the PR, alongside the project field information. Options A and C incorrectly assume the team understands the nuances of categorization vs. assignment, while option D misinterprets how project fields function.
13 / 25
Liam is reviewing a pull request for a new API endpoint. He notices the PR description states: 'Implement User Authentication'. The project field associated with this PR in GitHub Projects is set to 'Authentication'. A teammate asks Liam, 'Are you tracking the progress of authentication specifically through this project?' Which of the following best describes Liam's current usage and the intended purpose of setting the project field?
The question highlights a common misunderstanding about GitHub Projects. While project fields *can* be used to track progress on specific features, they are most effectively used at a higher level—to categorize and group related work. Setting the field to 'Authentication' indicates Liam is consciously tracking the progress of that particular feature area within the broader scope of the larger project; it's not simply a way to assign tasks but a way to *monitor* specific functional areas. Option A incorrectly suggests testing is independent of the project field, while options C and D misinterpret the primary function of project fields.
14 / 25
Alex: 'Hey team, I've created a GitHub Project for the 'Nova' redesign. I've added tasks for styling and front-end implementation. To help visualize our progress, I've set the project field to 'Front-End'. However, I'm getting feedback that it's not clear how this relates to the overall Nova project roadmap. Should I be using the project fields to track individual features within the larger redesign effort, or is there a better way to link these tasks to the broader goals?'This question addresses a common misunderstanding of GitHub Projects' purpose. While project fields *can* be used for granular tracking, their primary function is to provide strategic context – linking tasks to broader goals like 'Nova Redesign'. The incorrect options reflect the belief that they're solely for detailed task management or ignoring their strategic role entirely. The correct answer highlights the intended use of project fields as a way to connect individual features within a larger initiative, aligning with the overarching roadmap.
15 / 25
David: 'I've set up this GitHub Project for the 'Phoenix' migration. I've added tasks for database schema changes and data transformation. I'm using the 'Migration' project field to keep everything organized. Emily asks, 'Are you tracking all the individual steps of the migration within this project, or are you seeing it as a larger initiative?'This question tests understanding of how project fields are *intended* to be used. The core principle is that a project field represents an overarching initiative or category, not necessarily granular tasks. Options A and B misinterpret this by suggesting tracking every single step within the project, while option D incorrectly states the opposite – a project field should indeed provide a high-level overview. The correct answer reflects best practice: use the field for the overall migration and link related tasks as needed.
16 / 25
Sarah: 'Hey team, I've created a new GitHub Project called 'Feature X Development'. I've added a task for John to implement the core logic and another for David to write the unit tests. I want to track our progress closely, especially ensuring we're not falling behind on testing. Can someone explain how I can use GitHub Projects to visually monitor the status of these tasks and proactively identify potential roadblocks before they become major issues?'This scenario highlights a common misunderstanding – that GitHub Projects *only* track individual tasks. While you can certainly monitor progress with simple task status updates, the core value comes from visualizing workflow stages (like 'To Do', 'In Progress', 'Review', 'Done') using tools like Kanban boards.
Sarah is asking for a way to proactively manage her project and this option represents the most direct approach to achieving that visual monitoring.17 / 25
Mark: 'I've just created a new PR and added a comment to the title saying 'Needs Review – UI Changes'. I've also set the project field to 'UI/UX' so that the reviewers know what area to focus on. However, the team keeps asking me if I've assigned this task to anyone within GitHub Projects. What's the best way to clarify my intentions and ensure they understand how the project fields are being used?'This question addresses the common misunderstanding that project fields *automatically* assign tasks. While they provide context and categorize work for reviewers – like indicating 'UI/UX' is a priority – they don't replace actual task assignments within the PR itself. The correct answer clarifies this distinction, emphasizing that task assignment should still be set within the PR, alongside the project field information. Options A and C incorrectly assume the team understands the nuances of categorization vs. assignment, while option D misinterprets how project fields function.
18 / 25
Liam is reviewing a pull request for a new API endpoint. He notices the PR description states: 'Implement User Authentication'. The project field associated with this PR in GitHub Projects is set to 'Authentication'. A teammate asks Liam, 'Are you tracking the progress of authentication specifically through this project?' Which of the following best describes Liam's current usage and the intended purpose of setting the project field?
The question highlights a common misunderstanding about GitHub Projects. While project fields *can* be used to track progress on specific features, they are most effectively used at a higher level—to categorize and group related work. Setting the field to 'Authentication' indicates Liam is consciously tracking the progress of that particular feature area within the broader scope of the larger project; it's not simply a way to assign tasks but a way to *monitor* specific functional areas. Option A incorrectly suggests testing is independent of the project field, while options C and D misinterpret the primary function of project fields.
19 / 25
Alex: 'Hey team, I've created a GitHub Project for the 'Nova' redesign. I've added tasks for styling and front-end implementation. To help visualize our progress, I've set the project field to 'Front-End'. However, I'm getting feedback that it's not clear how this relates to the overall Nova project roadmap. Should I be using the project fields to track individual features within the larger redesign effort, or is there a better way to link these tasks to the broader goals?'This question addresses a common misunderstanding of GitHub Projects' purpose. While project fields *can* be used for granular tracking, their primary function is to provide strategic context – linking tasks to broader goals like 'Nova Redesign'. The incorrect options reflect the belief that they're solely for detailed task management or ignoring their strategic role entirely. The correct answer highlights the intended use of project fields as a way to connect individual features within a larger initiative, aligning with the overarching roadmap.
20 / 25
David: 'I've set up this GitHub Project for the 'Phoenix' migration. I've added tasks for database schema changes and data transformation. I'm using the 'Migration' project field to keep everything organized. Emily asks, 'Are you tracking all the individual steps of the migration within this project, or are you seeing it as a larger initiative?'This question tests understanding of how project fields are *intended* to be used. The core principle is that a project field represents an overarching initiative or category, not necessarily granular tasks. Options A and B misinterpret this by suggesting tracking every single step within the project, while option D incorrectly states the opposite – a project field should indeed provide a high-level overview. The correct answer reflects best practice: use the field for the overall migration and link related tasks as needed.
21 / 25
Sarah: 'Hey team, I've created a new GitHub Project called 'Feature X Development'. I've added a task for John to implement the core logic and another for David to write the unit tests. I want to track our progress closely, especially ensuring we're not falling behind on testing. Can someone explain how I can use GitHub Projects to visually monitor the status of these tasks and proactively identify potential roadblocks before they become major issues?'This scenario highlights a common misunderstanding – that GitHub Projects *only* track individual tasks. While you can certainly monitor progress with simple task status updates, the core value comes from visualizing workflow stages (like 'To Do', 'In Progress', 'Review', 'Done') using tools like Kanban boards.
Sarah is asking for a way to proactively manage her project and this option represents the most direct approach to achieving that visual monitoring.22 / 25
Mark: 'I've just created a new PR and added a comment to the title saying 'Needs Review – UI Changes'. I've also set the project field to 'UI/UX' so that the reviewers know what area to focus on. However, the team keeps asking me if I've assigned this task to anyone within GitHub Projects. What's the best way to clarify my intentions and ensure they understand how the project fields are being used?'This question addresses the common misunderstanding that project fields *automatically* assign tasks. While they provide context and categorize work for reviewers – like indicating 'UI/UX' is a priority – they don't replace actual task assignments within the PR itself. The correct answer clarifies this distinction, emphasizing that task assignment should still be set within the PR, alongside the project field information. Options A and C incorrectly assume the team understands the nuances of categorization vs. assignment, while option D misinterprets how project fields function.
23 / 25
Liam is reviewing a pull request for a new API endpoint. He notices the PR description states: 'Implement User Authentication'. The project field associated with this PR in GitHub Projects is set to 'Authentication'. A teammate asks Liam, 'Are you tracking the progress of authentication specifically through this project?' Which of the following best describes Liam's current usage and the intended purpose of setting the project field?
The question highlights a common misunderstanding about GitHub Projects. While project fields *can* be used to track progress on specific features, they are most effectively used at a higher level—to categorize and group related work. Setting the field to 'Authentication' indicates Liam is consciously tracking the progress of that particular feature area within the broader scope of the larger project; it's not simply a way to assign tasks but a way to *monitor* specific functional areas. Option A incorrectly suggests testing is independent of the project field, while options C and D misinterpret the primary function of project fields.
24 / 25
Alex: 'Hey team, I've created a GitHub Project for the 'Nova' redesign. I've added tasks for styling and front-end implementation. To help visualize our progress, I've set the project field to 'Front-End'. However, I'm getting feedback that it's not clear how this relates to the overall Nova project roadmap. Should I be using the project fields to track individual features within the larger redesign effort, or is there a better way to link these tasks to the broader goals?'This question addresses a common misunderstanding of GitHub Projects' purpose. While project fields *can* be used for granular tracking, their primary function is to provide strategic context – linking tasks to broader goals like 'Nova Redesign'. The incorrect options reflect the belief that they're solely for detailed task management or ignoring their strategic role entirely. The correct answer highlights the intended use of project fields as a way to connect individual features within a larger initiative, aligning with the overarching roadmap.
25 / 25
David: 'I've set up this GitHub Project for the 'Phoenix' migration. I've added tasks for database schema changes and data transformation. I'm using the 'Migration' project field to keep everything organized. Emily asks, 'Are you tracking all the individual steps of the migration within this project, or are you seeing it as a larger initiative?'This question tests understanding of how project fields are *intended* to be used. The core principle is that a project field represents an overarching initiative or category, not necessarily granular tasks. Options A and B misinterpret this by suggesting tracking every single step within the project, while option D incorrectly states the opposite – a project field should indeed provide a high-level overview. The correct answer reflects best practice: use the field for the overall migration and link related tasks as needed.
Frequently Asked Questions
What will I practise in "GitHub Projects — Vocabulary and Language"?
Learn the vocabulary of GitHub Projects: views, fields, iterations, and roadmaps.
How many exercises are in this module?
This module has 25 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more GitHub Platform Language exercises?
Browse the full GitHub Platform Language hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.