How to Set Up Jira for a Team That Has Never Used It Before

A team that has never touched Jira can be planning its work on a shared board in the first week, with every task visible, owned, and moving through the same stages. Jira's team-managed templates carry sensible defaults, so first-time setup is three moves:

Verified against Jira Cloud on 2026-08-22.

Prerequisites

Step 1: Pick Kanban or Scrum

For a team new to Jira, Kanban is the lighter starting point. A Kanban space can adopt sprints later, so nothing is lost by starting simple.

Step 2: Create the Space

  1. Hover over Spaces in the side navigation, then select Create space.
  2. In the template library, pick a category, find the Kanban or Scrum template, and select Use template.
  3. Give the space a name your team already uses for the work, such as the product or team name.
  4. Select Team-managed. Team-managed spaces are administered inside the space itself, which keeps configuration in the team's hands while they learn. The team-managed Kanban and Scrum templates include recommended defaults for work types, statuses, and views, and you can preview and adjust them before creating.
  5. Select Create.

Jira generates a space key, the short prefix that appears on every work item, and sets you as the space owner.

Step 3: Invite the Team

  1. In Atlassian Administration, select Invite users.
  2. Enter your teammates' email addresses and select the roles for the apps they need, then send the invitations.
  3. If someone invited to the site cannot see the space, add them directly: next to the space name, select More actions (•••) → Space settings → Access → Add people.

Step 4: Load Real Work

Skip sample data and enter the team's actual to-do list as work items, one per deliverable, each with an assignee. A board of real work is what makes the tool click for first-time users: the Monday question of who is doing what gets answered by the board instead of a meeting.

Step 5: Shape the Board to Match Reality

  1. Look at the default columns and compare them to how work actually moves through the team.
  2. In Space settings, rename statuses to the words the team already says out loud, and remove any column the team would skip.
  3. Resist adding columns for edge cases. A board with a handful of columns that everyone trusts beats a detailed one nobody updates.

Verify the Setup

If all three pass, the team is running on Jira.

Troubleshooting

This setup covers one team's first space. Standardizing across several teams, wiring in automation, or connecting a help desk is where configuration decisions start to compound, and it pays to configure for scale from day one. That is exactly the work ScaleIt does for startups and SMBs, including a fixed-price Jira Rescue for instances that grew without a plan.

Do you want Jira set up right the first time while your team stays focused on the work itself? We can help. Book a free call and we will map the setup to your team.

Verified against Jira Cloud on 2026-08-22. Vendor docs: https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/, https://support.atlassian.com/user-management/docs/invite-a-user/, https://support.atlassian.com/jira-software-cloud/docs/add-people-to-team-managed-projects/.