How to Create a Jira Board With Sample Data: 7 Steps (2026)

Wondering how to create a board with sample data on Jira? Follow 7 steps to build and test a realistic board. Click to discover!

Creating a Jira board can seem simple until you open an empty screen and wonder what to add first. Without sample work items, your columns, filters, and reports have nothing useful to display.

That empty board makes testing harder. You cannot tell whether your workflow matches your team’s process, whether cards contain enough detail, or whether a sprint view will stay readable.

But here’s the truth: you can create a realistic Jira board with sample information in seven practical steps. I’ll show you how to create the project, add representative issues, configure the board, and test the result before real work begins.

How to Create a Jira Board With Sample Information in 7 Steps

The fastest approach is to create a project, add a small set of realistic issues, connect the board to that project, and then test the workflow with different statuses and priorities.

Choose a Jira project type

Start by deciding whether you need a team-managed project or a company-managed project. Team-managed projects are usually easier for small teams because the team can configure many settings directly.

Company-managed projects offer more centralized control. They can suit organizations that need shared workflows, standardized fields, or consistent permission rules across several teams.

From the Jira dashboard, select Projects, choose Create project, and select a template such as Scrum, Kanban, or a general project template.

For a simple demonstration board, Kanban is often the clearest choice. It lets you move sample issues through stages without planning a sprint first.
Create the project and name it clearly

Give the project a name that explains its purpose. For example, use Website Redesign Demo rather than a vague label such as Test Project.

Choose a project key that is short and recognizable, such as WRD. Jira uses this key when creating issue identifiers like WRD-1 and WRD-2.

Add a brief project description so anyone opening the board understands the scenario. You could write, “Sample board for planning a product website redesign.”

Here’s why: clear naming makes sample work easier to distinguish from active work, especially when several projects appear in the same Jira account.
Add realistic sample issues

Open the project and select Create to add your first issue. Choose an issue type such as Story, Task, Bug, or Epic, depending on the workflow you want to test.

Use specific titles that resemble real work. For a website redesign, you might add these examples:
- Review the current homepage navigation
- Design a mobile checkout layout
- Fix the broken password reset link
- Write accessibility acceptance criteria
- Prepare analytics tracking requirements
- Run a usability test with five participants
Give each issue a different status, priority, assignee, and due date where possible. A board with every card in “To Do” will not help you evaluate movement across the workflow.
Connect the board to the project

Open the board menu and select the option for creating or finding a board. Choose a Scrum or Kanban board, depending on how you plan to manage work.

When Jira asks what the board should display, select the project you created. You may also be able to use a saved filter that includes selected projects, issue types, or labels.

For a basic sample board, a project-based board is easier to understand. It keeps your test issues together and reduces the risk of showing unrelated work.

You might be wondering: what if the board is empty? Check that the issues belong to the selected project and that the board filter includes their current statuses.
Configure columns and workflow statuses

Open the board settings and review the columns. A basic Kanban setup might include To Do, In Progress, In Review, and Done.

Map each Jira status to the column where it belongs. For example, map “Selected for Development” to To Do and “Code Review” to In Review.

Do not create a separate column for every possible status. Too many columns make the board difficult to scan and can hide the actual flow of work.

Move several sample issues through the columns. This exposes missing status mappings before your team depends on the board.
Set up filters, swimlanes, and card details

Use quick filters to answer common questions. Examples include “Only bugs,” “Assigned to me,” and “High priority.” Keep each filter focused on one useful question.

Swimlanes can separate work by epic, assignee, priority, or query. For example, grouping by assignee may help a small team spot uneven workloads.

Choose the card details that matter most, such as priority, assignee, issue type, labels, or story points. Avoid showing every available field.

The best part? You can test the board visually. If a card looks crowded or important information is hidden, adjust the layout before adding more issues.
Test the board with sample work

Move issues across the board as if you were running a normal workday. Assign a task, change its priority, add a comment, and mark a bug as resolved.

Then check whether the board, backlog, sprint view, and reports reflect those changes. A status may appear correct on one screen but fail to behave as expected elsewhere.

Try several edge cases. Move a task backward, reopen a completed issue, add a blocked label, and create a linked bug for an existing story.

Finally, remove or clearly label your sample issues. You can keep them for training, or delete them when the team is ready for live work.

What Sample Work Should You Add?

Useful sample work should resemble the size, language, and variety of your real work. Five identical tasks will not reveal much about board behavior.

For example, a product team could create one epic, three stories, two bugs, and two tasks. Give the issues different priorities and place them in different workflow stages.

Issue type	Example	What it helps you test
Epic	Improve account onboarding	Large work grouping and progress tracking
Story	Let customers verify their email address	User-focused acceptance criteria
Bug	Verification link returns an error	Defect priority and resolution flow
Task	Review email delivery metrics	Operational work outside feature development

Include at least one blocked issue and one completed issue. This gives you a quick way to examine labels, dependencies, status transitions, and completed-work reporting.

Let me explain: sample information is most valuable when it creates realistic decisions. A task that requires prioritization teaches you more than a card that merely fills an empty column.

How to Make the Board Resemble a Real Workflow

A board is useful when its columns represent decisions your team actually makes. “In Progress” should mean someone is actively working, while “In Review” should signal a specific handoff.

Write a short definition for each status. For example, an issue can enter In Review only after its acceptance criteria are complete and a reviewer has been assigned.

Consider a support team that uses New, Investigating, Waiting for Customer, and Resolved. Copying a software-development workflow would create confusion because the work moves differently.

Cause and effect matters here. If a status does not trigger a decision, handoff, or visible change, it may not deserve its own column.

How to Check Board Filters and Permissions

An empty or incomplete board often has a configuration problem rather than a content problem. The board may use a filter that excludes your project, issue type, status, or team.

Open the board filter and inspect its conditions. Look for project names, issue types, labels, assignees, and status restrictions that might hide your sample work.

Then test the board from another account or permission level if possible. A board that looks correct to an administrator may hide issues from contributors.

For example, if a tester can see WRD-1 but not WRD-2, compare the issue security settings and project permissions. This simple check can prevent an unpleasant surprise during launch.

How to Use the Board for Training and Testing

A sample board can become a short training environment. Ask a teammate to create an issue, assign it, move it through each status, and explain what should happen next.

Watch where they hesitate. Confusion often reveals unclear status names, missing field guidance, or an approval step that exists only in someone’s head.

You can also use the board to test reporting. Add estimates to several issues, complete one or two items, and inspect velocity, control charts, or cumulative flow views where available.

For example, if “Done” includes work that was never reviewed, your completion report may look healthier than the actual process. Sample work helps expose that mismatch safely.

Jira Board Alternative: ONES.com

ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project provides project management capabilities and can serve as a Jira alternative for teams that want configurable workflows, reporting, and self-hosted deployment choices.

ONES.com product screenshot

Value Proposition

If you are testing Jira with sample work because your team needs clearer planning and collaboration, ONES.com gives you another environment to evaluate. ONES Project is sold separately from ONES Wiki, so you can choose the product that matches your immediate needs.

Core Capabilities

Scattered work items → Jira-compatible workflows → Use familiar workflow concepts while organizing statuses, transitions, and handoffs in one project environment.
Limited visibility → Built-in reporting → Review progress, workload, and delivery trends without depending on a long list of separate plugins.
Rigid process rules → Custom workflows and fields → Adapt issue stages and information fields to product, engineering, marketing, or operations work.
Unclear iteration planning → Sprint management → Plan iterations, assign work, and review completed items through a structured sprint process.
Repetitive administration → Automation → Reduce routine actions by triggering assignments, status changes, or notifications when defined conditions occur.
Plugin-heavy setup → Native feature parity → Cover core planning and tracking needs with native capabilities, which can reduce dependency on extra extensions.
Restricted deployment requirements → On-premise and private cloud options → Run the platform in an environment that fits internal security, compliance, or network requirements.
Disconnected project knowledge → ONES Wiki → Pair project work with a knowledge management workspace when your team needs connected guidance, decisions, and technical context.

ONES.com supports up to 30 seats on its free plan and offers four deployment choices: Cloud, On-Premise, Private Cloud, and Air-gapped. The cloud and self-hosted versions provide full feature parity.

Application Scenarios

A software team moving beyond Jira can recreate its sprint workflow, issue types, custom fields, and reporting approach in ONES Project. The team can first test the process with representative sample work before inviting every contributor.

An organization with restricted networks may prefer an on-premise or air-gapped deployment. That approach lets the team manage project work inside its required environment instead of depending only on a public cloud setup.

A product organization may use ONES Project for delivery tracking and add ONES Wiki for shared knowledge. The separation keeps the project management and knowledge management products clear while supporting a connected working experience.

Common Challenges When Creating a Sample Jira Board

The board shows no issues

Problem: Your issues exist, but the board remains empty.

Solution: Check the project key, board filter, issue statuses, and permission settings. Confirm that the board columns include every status used by your sample issues.

The board becomes too crowded

Problem: Every card displays several fields, labels, links, and long titles.

Solution: Keep only decision-making details on the card. Open the issue when you need the complete description, comments, or activity history.

The workflow has too many stages

Problem: The board contains a separate column for every internal action.

Solution: Combine stages that do not change ownership or decision-making. Keep the visible workflow focused on meaningful progress.

Sample work looks unrealistic

Problem: Every issue has the same priority, assignee, and status.

Solution: Create a small but varied set of issues. Include a bug, a task, a story, a blocked item, and a completed item.

Sample issues remain after launch

Problem: Training cards become mixed with live work.

Solution: Add a clear label such as sample-board, keep the items in a dedicated project, or remove them before the team starts real delivery.

FAQs

Can I create a Jira board without adding real work?

Yes. Create a dedicated practice project and add fictional issues that resemble your team’s normal work. Use varied statuses, priorities, issue types, and assignees so the board behaves like a real working environment.

Should I use a Scrum or Kanban board for testing?

Choose Kanban when you want to test continuous flow, status transitions, and work-in-progress limits. Choose Scrum when you need to test a backlog, sprint planning, story points, sprint reporting, and review cycles.

How many sample issues should I create?

Start with eight to twelve issues. Include at least one epic, several stories or tasks, a bug, one blocked item, and one completed item. This is enough to test the main board behavior without creating unnecessary clutter.

Why are some Jira issues missing from my board?

The board filter may exclude the project, issue type, label, status, or assignee. Permissions can also hide issues. Review the filter and compare the missing issue’s project, status, and security settings with an issue that appears correctly.

Can I keep sample issues for training?

Yes, provided you label them clearly and separate them from active work. A dedicated training project is usually safest. If you keep them in a live project, a visible sample label can help prevent accidental updates or reporting errors.

Conclusion

Creating a Jira board with sample information takes seven practical moves: choose a project type, create the project, add realistic issues, connect the board, configure workflow columns, set filters, and test the process.

Start small, but make the examples varied. A board containing a bug, task, story, blocked item, and completed issue will reveal far more than a board filled with identical cards.

But here’s the truth: an empty board cannot prove that your workflow works. Add realistic examples, test the handoffs, and remove the training content before real delivery begins.

If Jira’s setup, deployment, or extension requirements do not fit your team, ONES Project is worth evaluating as a Jira alternative. It provides configurable project workflows, native reporting, automation, sprint management, and on-premise deployment options.