Plane Pages vs Work Items: Where Each Belongs

Plane pages and work items serve different purposes in project management: plane pages are for persistent, reference-style information (like wikis or documentation), while work items are for tracking discrete, actionable tasks with a lifecycle. You use a plane page when the content is meant to be read and maintained over time, and a work item when something needs to be done, assigned, and tracked to completion.

Background: Where the Confusion Comes From

The terms “plane page” and “work item” come from Azure DevOps, Microsoft’s set of development tools. In Azure DevOps, a “plane” is a conceptual layer that separates different types of data. The two main planes are the data plane (where work items live) and the content plane (where wiki pages, README files, and other documentation live). A “plane page” specifically refers to a page in the Azure DevOps wiki, which is a Markdown-based documentation space stored in a Git repository.

Work items, on the other hand, are the core tracking objects in Azure Boards. They include user stories, bugs, tasks, epics, and features. Each work item has a type, state, assignee, priority, and history. The confusion arises because both can be used to record information, but they have fundamentally different purposes and behaviors.

How Each Works

Plane pages (wiki pages):

• Stored as Markdown files in a Git repository (usually named .wiki)
• Version-controlled, so you can see every change and who made it
• No assignment, no state, no due date — just content
• Can be linked to from work items, but not vice versa (you can add a link to a work item in a page)
• Best for onboarding guides, architecture decisions, coding standards, and team processes

Work items:

• Stored in the Azure DevOps data store, not in Git
• Have a defined workflow (e.g., New → Active → Resolved → Closed)
• Can be assigned to a person, given a priority, and linked to other work items
• Support comments, attachments, and rich text descriptions
• Can be queried, charted, and used in sprints and backlogs

When to Use a Plane Page

Use a plane page when the information is reference material that the team needs to consult repeatedly. Common examples:

• Team onboarding checklist and environment setup steps
• Architecture decision records (ADRs)
• API documentation or coding conventions
• Release checklists that are the same every time (though you might also use a work item template)
• Incident post-mortems that are read for learning

A good rule of thumb: if you would put it in a README or a company wiki, it belongs on a plane page. If you would put it on a sticky note on a whiteboard, it belongs as a work item.

When to Use a Work Item

Use a work item when there is an action to complete with a clear definition of done. Examples:

• Implement a new feature (user story)
• Fix a bug (bug work item)
• Perform a specific task like “update the login page CSS” (task)
• Track a large initiative (epic or feature)

Work items are designed to answer: What needs to be done? Who is doing it? When is it due? What’s blocking it? They appear on boards and sprints, and they have a lifecycle that moves from to-do to done.

Common Problems and Misconceptions

Misconception: “I can just put instructions in a work item.” You can, but work items are ephemeral — they get closed and archived. If someone needs to find that instruction next month, they’ll have to search through closed work items. Plane pages persist and are easier to browse.

Problem: Documentation gets lost in work items. Teams often paste long explanations into a bug or task, then close it. The knowledge disappears. Instead, put the explanation on a plane page and link the work item to it.

Problem: Wiki pages become stale. Plane pages don’t have owners or due dates, so they can rot. A common fix is to add a “last reviewed” date or create a recurring work item to audit the wiki.

Problem: Work items used as documentation. Some teams create a work item for every piece of knowledge, leading to a cluttered backlog. This makes it hard to find anything and pollutes the board.

How to Choose: A Simple Decision Tree

1. Ask: “Is this something someone needs to do, or something someone needs to know?”
2. If it’s an action with a completion criteria → work item.
3. If it’s knowledge that will be referenced repeatedly → plane page.
4. If it’s both, put the knowledge on a plane page and create a work item that links to it.
5. If you’re still unsure, consider: would you want this to appear in a sprint board? If yes, work item. If no, plane page.

Practical Examples

Example 1: Onboarding a new developer. The step-by-step setup guide belongs on a plane page. The task “Set up local dev environment for new hire” is a work item assigned to the new hire, but the instructions live on the plane page.

Example 2: A bug fix. The bug report is a work item. The root cause analysis and the fix explanation should be written on a plane page (or in the code comments) so future developers can learn from it.

Example 3: Sprint planning. The sprint goals and team capacity are documented on a plane page. The individual stories and tasks are work items.

Frequently Asked Questions

Can I link a work item to a plane page?

Yes, you can add a link in a work item to a wiki page, and you can also add a link from a wiki page to a work item (using the work item ID). This is useful when a task depends on documentation or when documentation references a specific task.

Do plane pages count against storage limits?

Plane pages are stored in a Git repository, so they count against your Azure DevOps repository storage. Work items are stored in the data store and have a separate limit (currently 10 million per organization). In practice, wiki pages are small text files, so storage is rarely a concern.

Can I create a work item from a plane page?

Not directly from the wiki editor, but you can copy the URL and paste it into a work item description. Some browser extensions or custom scripts can automate this, but it’s not built-in.

Which is better for a team playbook?

A plane page (or a set of pages) is better for a team playbook because it’s meant to be read and maintained. Work items are for tracking actions, not for storing reference documents.

Can I have both a plane page and a work item for the same thing?

Yes, and it’s often the right choice. For example, you might have a plane page describing the release process and a work item for the current release’s specific tasks. The work item links to the page.

Do plane pages support permissions?

Yes, you can set permissions on the wiki repository, controlling who can read and edit. Work items have their own permission model based on area paths and iteration paths.

Related

• DeepSeek AI Explained: How It Works and Which Model to Use
• How to Choose an AI Assistant for Work, Study, or Life
• AI Infrastructure: Why the Chip Is Only Part of Performance