How to See Who's Out of Office in Jira

It is 9:15am Monday. You need to assign a critical bug fix. You open Jira, look at the team board, and realize you have no idea who is actually working today. Two people mentioned taking Friday off, but is anyone out today? You check Slack statuses. One person has a palm tree emoji. Another has nothing set. You send a message in the team channel: "Who's around this week?"

This is a daily friction point for engineering managers and scrum masters. Jira is where the work lives, but Jira has no native concept of who is available on any given day. The result is a patchwork of Slack statuses, Google Calendar events, and tribal knowledge that is never quite accurate.

Approach 1: Slack statuses and calendar blocks

The most common approach. People set their Slack status to "OOO" or "Vacation" and block time on their Google Calendar. Anyone who needs to know checks both places.

What works: Zero setup cost. Everyone already uses Slack and Calendar. It is better than nothing.

What breaks: Compliance is inconsistent. Not everyone remembers to set their status. Slack statuses expire or get overwritten. Calendar events are only visible to people with calendar access, which may not include all team members, especially across organizations. Most importantly, none of this is visible inside Jira, where the work assignment actually happens.

The failure mode is predictable: you assign a task to someone who is on vacation, and nobody notices until the task sits untouched for three days.

Approach 2: A shared "Who's Out" Jira dashboard

Some teams create a Jira dashboard with a filter showing all "Out of Office" issues for the current week. Each absence is a Jira issue with a start date and end date field. A JQL filter surfaces active absences.

What works: Absences are visible inside Jira. Managers can check the dashboard before sprint planning or task assignment. JQL makes it queryable.

What breaks: It requires discipline. Someone has to create an OOO issue for every absence, which means either the employee creates it (and some will not) or the manager creates it (and some will forget). The dashboard is only useful if the data is complete, and manually maintained data degrades over time.

It also mixes OOO issues with real work in the project, which adds clutter. With a team of 20, you might have 5 to 10 active OOO issues at any given time during summer months.

Approach 3: Dedicated out-of-office or calendar apps

Several Atlassian Marketplace apps provide team calendar views showing who is out. These range from simple calendar overlays to full leave management systems.

The simpler ones read from Google Calendar or let people manually mark dates in a calendar widget inside Jira. The more complete ones handle leave requests, approvals, and automatically show approved absences in a team view.

What works: Purpose-built UI for team availability. No manual issue creation. If the app handles leave requests too, the data is always current because it comes from the approval workflow.

What to watch for:

• Data source. Does the app read from another system (Google Calendar) or manage its own data? Reading from Calendar is convenient but inherits Calendar's accuracy problems (people forget to create events). Managing its own data through a leave request workflow is more reliable.
• Connect vs. Forge. Connect apps run on the vendor's infrastructure. Your team's absence data is stored on external servers. Forge apps run on Atlassian's infrastructure, so the data stays within your existing Atlassian trust boundary.
• Integration depth. Can you see availability from within a Jira project, or do you have to open a separate page? The value of team availability is highest when it is visible where you make assignment decisions.

What good team availability looks like

A team availability view that actually gets used has four properties:

• Automatically populated. When a leave request is approved, the person appears as out on those dates. No extra steps.
• Visible inside Jira. Not a separate URL, not a different app, not a dashboard you have to remember to check. It should be accessible from the project where you assign work.
• Holiday-aware. Public holidays should be reflected in the availability view. If Monday is a national holiday, the entire team is unavailable that day. This matters for capacity planning.
• Team-scoped. A manager should see their team's availability, not the entire company's. A 200-person company calendar is noise. A 6-person team view is useful.

How TeamOps handles this

TeamOps builds team availability into the leave management workflow. When a leave request is approved, the employee automatically appears as out on those dates. Managers see a team-level view of who is available and who is not, directly inside their Jira project.

Public holidays are included automatically based on the team's configured country. Custom holidays (company offsites, team days) can be added. The result is a single view that answers "who is available this week?" without checking Slack, Google Calendar, or a spreadsheet.

Because TeamOps is Forge-native, the availability data stays on Atlassian's infrastructure. There is no external server storing your team's absence patterns.

For teams evaluating different approaches, the comparison page breaks down how TeamOps compares to standalone calendar apps and full HRIS platforms.