Jira Setup & Configuration Guide

Step-by-step Jira setup for a small software development team

1. Recommended Jira Strategy for a Small Team

For a small software team, avoid creating a complicated Jira configuration. Start with a single project and a simple workflow.

1 Jira Project Scrum or Kanban Epic Story Task Bug 3–5 Statuses Simple Dashboard
AreaRecommended Starting Configuration
ProjectOne Jira Software project
MethodologyScrum for sprint-based delivery; Kanban for continuous flow
Issue TypesEpic, Story, Task, Bug, Sub-task
WorkflowTo Do → In Progress → Code Review → QA → Done
PriorityHighest, High, Medium, Low, Lowest
EstimationStory Points
Sprint2 weeks is a good starting point
ReleaseVersions such as 1.0.0, 1.1.0
DashboardAssigned Work, Sprint Progress, Created vs Resolved
Small-team principle: Jira should make work visible, not create additional administrative work.

2. Create the Jira Project

Step 1 — Sign in

Open your organization's Jira site and sign in with an administrator or project-admin account.

Step 2 — Create project

Use the Jira project creation option and select a software project template.

For a sprint-based development team, select a Scrum template.

For a team handling support tickets, maintenance and continuously arriving work, select a Kanban template.

Step 3 — Project name

Example:

FRT Test Series

Step 4 — Project key

Example:

FRT

Jira issues will then look like:

FRT-101
FRT-102
FRT-103

Step 5 — Project description

Example:

FRT Test Series - Spring Boot Microservices
Development, QA, deployment and production support tracking.
Choose the project type carefully because Jira's available configuration, permissions and administration options can differ between project types and Jira plans.

3. Add Team Members

For a small team, keep membership simple.

Team MemberTypical Jira Responsibility
Product OwnerRequirements, backlog priority, acceptance
Tech LeadTechnical planning, review, architecture
Backend DeveloperStories, tasks, bugs, implementation
Frontend DeveloperUI stories/tasks
QA EngineerTesting, defects, acceptance validation
DevOpsCI/CD, environments, deployment tasks

Step-by-step

  1. Open project settings.
  2. Open people/members or access management.
  3. Invite team members.
  4. Assign appropriate project roles.
  5. Verify that each member can create and update issues.
Do not give every team member Jira administration privileges. Most developers need project access, not global Jira administration access.

4. Configure Project Roles

A simple role model is sufficient.

RoleSuggested MembersMain Responsibilities
Administrator1–2 trusted peopleProject configuration
Product OwnerPOBacklog and priorities
DeveloperDevelopersImplementation
QATestersTesting and defects
ViewerStakeholdersRead-only visibility where needed
Use groups where your Jira plan and organization structure make them useful. Avoid manually configuring dozens of individual permission entries.

5. Configure Issue Types

For a small development team, the following issue types are usually enough.

Issue TypePurposeExample
EpicLarge feature or business capabilityOnline Test Attempt
StoryUser-facing requirementCandidate can submit test
TaskTechnical or operational workConfigure Redis connection
BugDefectOTP validation returns 401
Sub-taskSmaller part of an issueWrite unit tests

Recommended hierarchy

EPIC
 |
 +-- STORY
 |    |
 |    +-- SUB-TASK
 |    +-- SUB-TASK
 |
 +-- STORY
 |
 +-- TASK
 |
 +-- BUG
Do not create separate issue types such as "Java Task", "DB Task", "API Task", "Deployment Task", "Testing Task" unless there is a real reporting or workflow need. Use Components, labels and fields instead.

6. Configure a Simple Workflow

Recommended workflow for a small Spring Boot/microservices team:

TO DO
  |
  v
IN PROGRESS
  |
  v
CODE REVIEW
  |
  v
QA
  |
  v
DONE

Status meanings

StatusMeaning
To DoReady to be started
In ProgressDeveloper is actively working
Code ReviewImplementation completed and pull request is under review
QAReady for or undergoing testing
DoneAcceptance criteria completed and issue is closed

Optional status

BLOCKED

Use Blocked only when work genuinely cannot proceed. Do not use it as a general waiting status.

A smaller workflow is easier to understand and report. Avoid creating statuses such as "Developer Testing", "Ready for Deployment", "Deployed to DEV", "Deployed to QA", "UAT", "Ready for Production", etc. unless those states are operationally important and consistently maintained.

7. Configure the Scrum/Kanban Board

Scrum board

Use Scrum when the team plans work into fixed sprints.

Example columns:

TO DO | IN PROGRESS | CODE REVIEW | QA | DONE

Kanban board

Use Kanban when work arrives continuously and sprint commitments are less important.

Example:

BACKLOG | READY | IN PROGRESS | REVIEW | QA | DONE

Column configuration

Map Jira statuses to board columns so that every issue has a clear visual position.

For a small development team doing planned feature development, Scrum + 2-week sprints is a practical starting point.

8. Create and Manage the Backlog

Step 1 — Create Epic

Example:

Epic: Online Test Management

Step 2 — Create Stories

FRT-101 Candidate can start a test
FRT-102 Candidate can answer questions
FRT-103 Candidate can submit a test
FRT-104 Candidate can view test result

Step 3 — Create technical tasks

FRT-105 Configure Redis caching
FRT-106 Add database index
FRT-107 Configure API Gateway route

Step 4 — Create bugs

FRT-108 OTP validation returns HTTP 401
FRT-109 Test submission fails for large payload

Step 5 — Prioritize

Order the backlog according to business value and technical urgency.

The Product Owner should normally own business priority, while the technical team should provide effort, risk and dependency information.

9. Write a Good User Story

Recommended format

As a <user>,
I want <capability>,
So that <business value>.

Example

Title:
Candidate can submit an online test

Description:
As a candidate,
I want to submit my completed test,
So that my answers can be evaluated.

Acceptance Criteria:
1. Candidate can submit the test.
2. Submission is stored successfully.
3. Duplicate submission is prevented.
4. Candidate receives a successful response.
5. Submission timestamp is stored.
6. Appropriate error response is returned on failure.
A good Jira story should be understandable without requiring the developer to guess what "done" means.

10. Bug Management

Recommended bug information:

FieldExample
SummaryOTP validation returns 401 after valid OTP
EnvironmentQA
SeverityHigh
PriorityHigh
Steps to ReproduceLogin → enter OTP → submit
Expected ResultAccess token generated
Actual ResultHTTP 401 returned
EvidenceLogs/screenshots/request IDs

Bug workflow

TO DO → IN PROGRESS → CODE REVIEW → QA → DONE

If QA rejects the fix:

QA → IN PROGRESS → CODE REVIEW → QA

11. Configure Sprints

Recommended sprint duration

2 weeks

Before sprint planning

Create sprint

  1. Open Backlog.
  2. Create Sprint.
  3. Move selected stories/tasks into the sprint.
  4. Confirm sprint goal.
  5. Start Sprint.

Example Sprint Goal

Sprint Goal:
Complete online test submission flow and stabilize OTP authentication.

During sprint

Developers update issues as work progresses:

TO DO → IN PROGRESS → CODE REVIEW → QA → DONE

End of sprint

12. Story Points and Estimation

Use relative estimation rather than estimating every story directly in hours.

Recommended scale

1 → Very small
2 → Small
3 → Moderate
5 → Medium/Large
8 → Large
13 → Very large — consider splitting

Example

StoryPoints
Add simple API validation2
Add OTP validation flow5
Implement complete test submission workflow8
Large multi-service redesign13+
Avoid using story points as individual performance scores. Story points represent relative effort/complexity and uncertainty, not employee productivity.

13. Components

Components are useful for identifying technical areas without creating many issue types.

ComponentExample Work
API GatewayRoutes, authentication filters
Auth ServiceLogin, OTP, JWT
OrchestratorBusiness orchestration
Test ServiceTests, questions, attempts
DatabaseSchema and SQL
DevOpsJenkins, Docker, Nginx
Use Components for stable areas of ownership. Use Labels for temporary or cross-cutting classifications.

14. Labels

Examples:

authentication
jwt
redis
mysql
performance
security
deployment
production
technical-debt
Do not create hundreds of labels. Agree on a small vocabulary and reuse it consistently.

15. Versions and Releases

Use Jira Versions to represent software releases.

Example

1.0.0
1.1.0
1.2.0
2.0.0

Example mapping

Epic: Online Test Management
 |
 +-- FRT-101 → Fix Version 1.1.0
 +-- FRT-102 → Fix Version 1.1.0
 +-- FRT-103 → Fix Version 1.1.0

Release process

  1. Create version.
  2. Assign relevant issues.
  3. Complete development.
  4. Complete QA.
  5. Deploy release.
  6. Close the version when released.

16. Jira Dashboard

A small team does not need a complicated dashboard.

Recommended gadgets/widgets

Dashboard ElementPurpose
Assigned to MePersonal work
Filter ResultsImportant issues
Created vs ResolvedIssue trend
Pie ChartIssues by status/priority
Sprint ProgressCurrent sprint visibility
RoadmapEpic/release overview

Useful saved filters

project = FRT AND assignee = currentUser() AND resolution = EMPTY

project = FRT AND status != Done

project = FRT AND priority in (Highest, High)

project = FRT AND issuetype = Bug AND status != Done

project = FRT AND sprint in openSprints()
The exact JQL functions and available dashboard gadgets depend on your Jira product/version and plan.

17. Permissions

For a small team, keep permissions simple.

CapabilityRecommended Access
Browse ProjectAll project members
Create IssuesDevelopers, QA, PO
Edit IssuesTeam members
Transition IssuesTeam members according to workflow
Manage SprintsScrum Master/Team Lead/PO as agreed
Project Administration1–2 trusted admins
Do not grant project administration or global Jira administration privileges to every developer.

18. Integrate Jira with Git

Use Jira issue keys in Git branch names, commits and pull requests.

Branch naming

feature/FRT-101-test-submission
bugfix/FRT-108-otp-401
hotfix/FRT-115-production-login

Commit example

FRT-101 Implement test submission API

Pull request title

FRT-101 Implement test submission API
When Jira's development integration is configured, consistent issue keys make it much easier to navigate from Jira → branch → commit → pull request → build/deployment.

19. Jira + Jenkins Integration

A useful CI/CD flow is:

Jira Issue
   |
   v
Git Branch
   |
   v
Pull Request
   |
   v
Jenkins Build
   |
   v
Automated Tests
   |
   v
QA
   |
   v
Deployment

Recommended convention

Jira:
FRT-101

Git:
feature/FRT-101-test-submission

Commit:
FRT-101 Add test submission API

Jenkins:
Build #245

Release:
1.1.0
Use the Jira/Git/Jenkins integration capabilities available in your Jira plan and installed integrations. Avoid building custom automation until the standard integration is insufficient.

20. Complete Example — Spring Boot Microservice Story

Epic

EPIC: Online Test Submission

Story

FRT-101
Title: Candidate can submit completed test

Description:
As a candidate,
I want to submit my completed test,
So that my answers can be evaluated.

Acceptance Criteria:
1. Candidate can submit the test.
2. Answers are persisted.
3. Submission time is stored.
4. Duplicate submission is prevented.
5. API returns an appropriate response.
6. Unit tests are implemented.

Sub-tasks

FRT-101-1 Implement REST endpoint
FRT-101-2 Implement service logic
FRT-101-3 Implement repository changes
FRT-101-4 Add unit tests
FRT-101-5 Add integration tests
FRT-101-6 Update API documentation

Development flow

FRT-101
   |
   +-- Git branch: feature/FRT-101-test-submission
   |
   +-- Pull Request
   |
   +-- Jenkins Build
   |
   +-- Unit Tests
   |
   +-- Code Review
   |
   +-- QA
   |
   +-- Done

21. Daily Team Process

Daily Stand-up

Each team member should briefly cover:

  1. What did I complete?
  2. What am I working on?
  3. Am I blocked?

Jira update rule

Update the Jira issue before or during the stand-up so the board reflects reality.

Good practice: If someone says "I am working on FRT-101", the Jira board should also show FRT-101 as In Progress.

22. Small-Team Jira Ceremonies

ActivitySuggested FrequencyDuration
Sprint PlanningEvery 2 weeks45–90 min
Daily Stand-upDaily10–15 min
Backlog RefinementWeekly30–45 min
Sprint ReviewEvery 2 weeks30–60 min
RetrospectiveEvery 2 weeks30–45 min
Adjust these durations to the actual team size and workload. The goal is effective communication, not filling calendars.

23. Jira Best Practices for a Small Team

24. Things to Avoid

AvoidPrefer
20+ workflow statuses3–5 meaningful statuses
Many custom issue typesEpic/Story/Task/Bug/Sub-task
Huge descriptions for simple tasksClear objective and acceptance criteria
Story points as performance metricsStory points for planning
Updating Jira only at sprint endUpdate as work progresses
One project per microserviceOne project for a small product/team initially
Uncontrolled labelsSmall agreed label vocabulary

25. Complete Jira Setup Checklist

Initial Setup

Team

Project Configuration

Process

Integration