A Step-by-Step Guide to Using Atlassian's Jira Software
Unsure where to start with Jira? Learn to set up projects, organize work, and run boards with atlassian software jira. Read now to get started!
Jira Software can help you organize projects, but getting started can feel confusing when boards, work items, and workflows all appear at once. A poorly set-up project can bury priorities, leave teammates unsure what to do next, and make progress harder to measure.
That confusion grows when you choose the wrong project template or launch a sprint before your backlog is ready. The good news is that you can learn Jira one practical step at a time. Here's the truth: you don’t need to customize everything on day one. I’ll show you how to create a project, organize work, run a board, and use reports to keep your team moving.
How to Use Jira Software: A Step-by-Step Guide
Start with a clear project goal, choose a suitable template, and add only the work your team needs to manage. Then use the board and reports to guide daily decisions.

1. Create a project for a clear goal
In Jira, create a project for a product, team, or defined body of work. Choose a name that teammates will recognize, such as “Mobile App Launch” or “Customer Support Improvements.”
Project creation options and menu labels can vary by Jira plan and interface version. If you’re unsure which setting to choose, start with a team-managed or company-managed project that fits your team’s needs.

2. Choose Scrum or Kanban
Pick Scrum if your team plans work in time-boxed sprints. Choose Kanban if work moves continuously through stages, as it often does in support or maintenance teams.
For example, a product team releasing features every two weeks may prefer Scrum. A small operations team handling requests as they arrive may find Kanban easier to maintain.
3. Set up the board and workflow
A board gives your team a visual view of work and its current status. Common columns include “To Do,” “In Progress,” and “Done,” but you can adjust them to reflect your actual process.
Keep the first workflow simple. If every task must pass through seven columns, teammates may spend more time updating statuses than moving work forward.
4. Add and describe work items
Create work items for the tasks, bugs, and features your team needs to track. Give each one a specific summary, a useful description, a priority, and an owner when appropriate.
“Fix checkout error on mobile” is more actionable than “Checkout.” Add acceptance criteria or relevant context so the person assigned can understand what completion means.
5. Organize the backlog and plan work
In a Scrum project, review the backlog before starting a sprint. Put urgent or high-value work near the top, check that tasks are understood, and estimate effort if your team uses estimates.
During sprint planning, select a realistic amount of work. A team that finishes six well-chosen tasks can make steadier progress than one that commits to twelve and carries most of them forward.

6. Update work during the sprint or workday
Move work across the board as its status changes. Assign tasks clearly, add comments when decisions affect the work, and flag blockers early so teammates can respond.
For example, if a developer is waiting for a design decision, mark the task as blocked and explain what’s needed. That makes the delay visible instead of leaving the task unchanged on the board.
7. Review progress and improve the process
Use Jira reports to inspect progress, spot bottlenecks, and discuss what the team should change. Scrum teams might review a sprint report after completion, while Kanban teams can examine flow and work in progress.
Treat a report as a prompt for conversation, not a scorecard. If work repeatedly stalls in review, discuss whether reviews need clearer ownership or fewer handoffs.
Choose a Jira Project Type That Fits Your Team
The project setup shapes how your team organizes and views work. Scrum and Kanban are common starting points, but the right choice depends on how work arrives and gets completed.
Scrum works well when a team plans a defined set of work for each sprint. Kanban suits ongoing work that enters the queue at different times, such as bug fixes or internal service requests.
Here’s why: a familiar template can help you begin quickly, while a mismatched one can add unnecessary planning. If your team rarely estimates or plans iterations, a sprint-based setup may create extra upkeep.
Write Work Items That Give Teammates Direction
A useful work item tells someone what needs attention and why. Include the expected result, any relevant constraints, and a clear owner when the task calls for one.
For example, “Add password reset link to the sign-in page” gives a developer more direction than “Improve login.” A short description can also explain where the link should appear and what should happen after someone selects it.
Keep each item small enough to understand and review. If “Launch new checkout” spans design, development, testing, and release, split it into tasks that show those distinct pieces of work.
Run Sprints and Boards Without Creating Extra Busywork
A sprint or board should help your team make decisions, not become a separate chore. Agree on what each status means, who updates work, and how your team handles blockers.
The best part? You can improve the workflow gradually. Start with a few clear columns, then add a status only when the team needs it to show a meaningful handoff or decision.
For a support team, a “Waiting for Customer” column may reveal why requests are paused. For a product team, a dedicated review status can show whether completed development work still needs approval.
Use Reports to Spot Delays and Discuss Improvements
Jira reports can help you see how work moves through a project and whether planned work gets completed. Choose a report that answers a specific question rather than opening every chart available.
If a sprint ends with unfinished work, look at what changed during planning and where tasks became blocked. If Kanban work piles up in one column, the team may need to review capacity or clarify ownership.
Reports are most useful when you discuss the reasons behind a pattern. A chart can show that tasks waited several days in review; a conversation can reveal that reviewers lacked clear responsibilities.
Customize Jira Carefully as Your Process Changes
Jira supports workflows, fields, and automation that can reflect a team’s process. Begin with the simplest setup that makes work visible, then add custom elements to solve specific, recurring problems.
Let me explain: a custom field is helpful when the team regularly needs information that standard fields don’t capture. An automation rule can reduce repetitive updates, such as notifying an owner when work reaches a particular status.
Before adding a rule or field, ask who will maintain it and how it changes the team’s decisions. Too many custom options can make it harder for new teammates to understand what they need to update.
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative; the products are sold separately.

For teams weighing Jira alongside other project management approaches, the practical questions are familiar: can you shape workflows, keep work visible, and run the product in the environment your organization requires? ONES.com offers Cloud, On-Premise, Private Cloud, and air-gapped deployments, with feature parity between its cloud and self-hosted versions. Its free plan supports up to 30 seats.
Core capabilities
- Workflow changes are difficult to manage: ONES Project supports Jira-compatible workflows, giving teams room to map work stages to their established process and keep handoffs visible.
- Standard fields miss team-specific details: Custom fields let teams capture information relevant to their work, helping teammates find needed context within the project.
- Planning work across iterations takes extra coordination: Sprint management helps teams organize iteration work and review progress in the same project environment.
- Teams need clearer progress visibility: Built-in reporting gives teams ways to review project activity and discuss where work may be slowing down.
- Repeated status changes consume time: Automation can handle routine workflow actions, reducing manual updates for recurring situations.
- Multiple add-ons complicate project setups: A platform with native project capabilities can reduce reliance on plugins for supported needs, simplifying administration.
- Cloud-only deployment doesn’t meet every requirement: On-Premise, Private Cloud, and air-gapped options provide deployment choices for teams with different infrastructure needs.
- Teams want to connect project work with knowledge management: ONES.com brings project and knowledge management into a unified platform, while ONES Project and ONES Wiki remain separately sold products.
Application scenarios
A product team moving from Jira can assess whether ONES Project’s Jira-compatible workflows, custom fields, sprint management, reporting, and automation fit its existing routines. A small team can also try the free plan, which supports up to 30 seats.
An organization with restricted network requirements can consider an air-gapped or self-hosted deployment. It can evaluate the available deployment options and feature parity against its operational needs before choosing an environment.
Common Challenges When Getting Started
Too many statuses make the board hard to read
Problem: Teammates have trouble choosing the right status, and tasks appear scattered across similar columns.
Solution: Review each status with the team and remove or combine stages that don’t represent a meaningful change in work. Keep the board easy to understand for someone joining the project.
Work items are too vague to act on
Problem: A task such as “Improve performance” leaves the assignee guessing about the expected result.
Solution: Rewrite it with a specific outcome, such as “Reduce product search loading time on mobile.” Add acceptance criteria if the team needs a shared definition of done.
Sprints repeatedly carry unfinished work forward
Problem: The team commits to more work than it can complete or regularly encounters unexpected dependencies.
Solution: Review previous sprint outcomes and discuss what affected delivery. Reduce the next sprint’s commitment when needed, and make dependencies visible during planning.
Automation creates unexpected changes
Problem: A rule updates a work item or sends notifications in situations the team didn’t expect.
Solution: Test the rule with a limited set of work, explain its purpose to teammates, and check its activity after launch. Turn it off if it creates confusion or duplicate actions.
Frequently Asked Questions
Is Jira Software suitable for a small team?
Yes. A small team can use Jira to plan tasks, track bugs, and show who owns current work. Start with a simple project and a short workflow instead of configuring every available option. As your team grows, review whether you need sprints, additional fields, automation, or more detailed reporting. The right setup is the one your teammates can keep accurate without excessive upkeep.
Should I use Scrum or Kanban in Jira?
Choose Scrum if your team plans work in fixed-length iterations and reviews results at the end of each sprint. Choose Kanban if tasks arrive continuously and move through stages as capacity allows. For example, a feature team may plan two-week sprints, while a service team handles incoming requests through a continuous queue. Consider how your work arrives before choosing a board.
Can I customize Jira workflows and fields?
Jira allows teams to customize workflows and fields, though available options can depend on project type, permissions, and plan. Add a field when the team consistently needs information that its current setup doesn’t capture. Add a workflow stage when it represents a real handoff or decision. Keep a clear reason for each change so the project remains understandable.
How can I keep a Jira board useful?
Use statuses that reflect actual work, write specific task summaries, and update items when their status changes. Review the board regularly to identify stale tasks, blockers, or repeated delays. For instance, if tasks remain in review for days, discuss ownership and review expectations with the team. A short, consistent maintenance habit can make the board more reliable.
Conclusion
Jira Software becomes easier to use when you begin with a clear goal, choose a project type that fits your work, and keep your board understandable. Specific work items and regular updates help teammates see what needs attention.
But here's the truth: no project setup will prevent every delay. Review your reports, discuss what’s slowing the team down, and adjust the workflow only when a change solves a real problem. If Jira doesn’t match your deployment or project needs, compare alternatives such as ONES Project and assess their workflows, capabilities, and hosting options.