iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To track a project in Jira Cloud, choose a space and template that fit the work, create clear and appropriately sized work items, and keep their owners and statuses current. Use a board to follow day-to-day progress, a timeline to plan dates and dependencies where available, and reports to investigate specific questions about delivery or workflow.
Choose the right Jira space and setup
Jira Cloud’s current documentation calls its organizing container a space; some screens or teams may still use familiar terms such as “project” or “issue.” Atlassian defines a space as a collection of related work items used to organize, track, and manage work. A space might represent a product, project, team, or service. Atlassian Support: What is a Jira space?
| Choice | Best fit | What it changes |
|---|---|---|
| Business space | General business or nontechnical project work | Offers project-management-oriented templates and views. |
| Software space | Software development | Includes templates such as Scrum, Kanban, and bug tracking, with development-oriented boards and reporting. |
| Team-managed | A team that needs to configure its own space | Configuration is managed locally by the team. |
| Company-managed | Organizations that need shared administrative standards | Configuration is governed through broader administration and can be shared across spaces. |
The available options and controls depend on the space type and your permissions. Before following a particular set of interface steps, check which kind of space you have and whether it is team-managed or company-managed. For a general business project, start with a business project-management template; for software work, select Scrum, Kanban, or bug tracking according to how the team handles incoming and in-progress work. Atlassian Support explains Jira space types and management models.
Create work items that can be tracked
A tracker is only useful when each work item describes work that someone can own and move through the team’s process. Keep the description specific enough to show what needs to be done and how the team will recognize completion. Split large efforts into smaller work items; use subtasks when a single item needs detailed steps.
#1 Best Overall
- Owner: Assign a person when responsibility is clear. Unassigned work can be harder to move forward.
- Priority: Set it when the team needs to distinguish urgent work from the rest of the queue.
- Dates: Add due dates for time-sensitive commitments. Use start and due dates when planning work on a timeline that supports them.
- Labels: Apply consistent labels when they will help group or filter related work.
- Attachments: Add relevant files or context when they help someone complete the work.
These fields are tools, not a checklist every item must satisfy. Add only the information that helps the team coordinate, plan, or report on that work. Atlassian’s business project-management guidance covers work items, subtasks, dates, priorities, and related tracking practices. Use business projects for project management.
Track daily progress on a board
A board gives the team a current view of work grouped by workflow status. In a simple project-management workflow, the states might be To do → In Progress → Done. Read the columns as the team’s agreed workflow, then move each work item when its real status changes. A board is most useful when it reflects the work as it is happening, rather than serving as a separate plan that nobody updates.
- Open the board for the space or team whose work you want to monitor.
- Review items in each status column to see what is waiting, underway, or complete.
- Move an item to the next status when the work actually changes state.
- Review the queue and priorities with the team, and adjust the workflow configuration if its columns no longer match how work is handled.
Software-space boards display work items as cards organized by status; the exact board setup and which work appears depend on its configuration. If an expected item is missing, check the board’s filter and the space’s permissions before assuming the work was deleted. Atlassian’s board guidance describes the board’s role and behavior. What is a board in software spaces?
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Plan dates and dependencies on a timeline
Use a timeline when the team needs to look beyond the current flow of work: schedule work across dates, see how items relate, or identify dependencies where the space supports them. A board answers “What is happening now?”; a timeline helps answer “What is planned, and what depends on what?” Set relevant start and due dates, arrange related items, and link dependencies if that capability is available in your setup.
Timeline behavior differs between business and software spaces. Standard software timelines are scoped to work in one space, so they should not be treated as a cross-space plan. Atlassian documents broader cross-space planning through eligible Jira plans, with availability subject to plan entitlements. Check the current plan and permissions if you need to coordinate work across spaces. Software-space timeline guidance and timeline limits in Jira describe the relevant scope and restrictions.
Choose reports by the question you need answered
Jira reports are more useful when you start with a specific question instead of treating one chart as a universal progress score. Available reports depend on the space type and configuration.
| Question | Report or view to consider | What it helps you inspect |
|---|---|---|
| How is the current sprint progressing? | Sprint or burndown report | Work completed against the sprint’s remaining work over time. |
| Has the scope changed during the effort? | Burnup report | Completed work alongside changes in total scope. |
| How long does work take, or where is it accumulating? | Control chart or cumulative flow diagram | Work-flow patterns and items building up between statuses. |
| How is a larger initiative progressing? | Epic report | Progress across work associated with an epic. |
| What is the outlook for a release? | Version report | Work associated with a version or release. |
Velocity can help a software team forecast how much work to plan in future sprints, but it is an estimate based on configured work and historical data—not a promise that a particular amount will be delivered. Reports surface signals; they do not guarantee a completion date. See Atlassian’s guide to tracking and analyzing work with reports.
Recommended Free Tools
Keep the tracker dependable
- Update status when work changes, and keep ownership current when responsibility moves.
- Maintain dates that inform scheduling, rather than leaving outdated commitments in place.
- Use labels and filters consistently so the team can focus on relevant work.
- Check board filters when stakeholders say expected items are missing; a board may not display every item in a space.
- Confirm the space type, management model, permissions, and enabled views before relying on a feature-specific instruction.
These habits keep the board, timeline, and reports grounded in the same current set of work instead of allowing each view to tell a different story.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
