Frequently Asked Questions

TeamOps is installed from the Atlassian Marketplace by a Jira site administrator:

1. Go to Atlassian Marketplace and search for "TeamOps."
2. Click Get it now (or Try it free if using a paid tier).
3. Select your Jira site and confirm the installation.
4. Once installed, all users can access TeamOps through Apps > TeamOps HR Portal.

Only Jira site administrators can install apps. If you are not a site admin, ask your Jira administrator to install it for you.

TeamOps auto-configures itself the first time it is opened:

• Country detection: Identifies your country from your Jira locale.
• Public holidays: Loads the current year's public holidays for your country.
• Default leave types: Creates Annual Leave, Sick Leave, and Personal Leave with standard allocations.
• Work week: Sets Monday through Friday as the default.
• Onboarding templates: Makes five built-in templates available (Engineering, Sales, General, HR, Executive).

No manual setup is required to start using the app.

The person who installs TeamOps is automatically the first HR Admin. After that, any existing HR Admin can add others via TeamOps Settings > Access & Roles > Add Member.

HR Admin access in TeamOps is separate from Jira site administration.

Yes. TeamOps works on both Jira Software and Jira Service Management (JSM). It is installed at the site level and is available to all Jira products on your site.

Yes. When starting an onboarding or offboarding, you can link it to any Jira project on your site. Different onboardings and offboardings can be linked to different projects. Leave management is not project-specific -- it works across your entire Jira site.

There is no hard limit. You can create as many as your organization needs (Annual Leave, Sick Leave, Parental Leave, Bereavement Leave, etc.). We recommend keeping the list to 5-10 types for simplicity.

TeamOps counts all days between your start and end date (inclusive), then subtracts:

1. Weekend days (or your configured non-work days)
2. Any public or custom holidays in that range

Example: Monday to Friday with a Wednesday public holiday = 4 business days.

Yes, as long as the leave period has not already started. Go to Leave Requests, find the request, and click Cancel. If it was already approved, the days are returned to your balance. You cannot cancel leave that is in progress or in the past.

Nothing. Your balance is only reduced when a request is approved. Pending and rejected requests do not affect your available balance.

Yes. Managers can view leave balances for their direct reports. They cannot see balances for employees outside their team. HR Admins can see balances for all employees.

Yes. HR Admins can create custom templates from scratch or by duplicating one of the five built-in templates. See the Admin Guide for step-by-step instructions.

When you link a Jira project:

• A Jira issue is created for each onboarding task.
• Task status syncs in both directions between TeamOps and Jira.
• Tasks appear on the project's board and backlog.
• Assignees receive standard Jira notifications.

Linking a project is optional. Without it, tasks are tracked entirely within TeamOps.

TeamOps runs a daily check for overdue tasks. When a task is overdue: the task is highlighted in red, the assigned person gets a Jira notification, and the manager and HR Admin are also notified. Reminders repeat daily until the task is completed.

Yes. HR Admins and Managers can reassign any task by clicking Edit on the task and changing the assignee. The new assignee receives a notification.

All data is stored within Atlassian's Forge platform on Atlassian's infrastructure (AWS). Your data:

• Lives within the same security boundary as Jira itself
• Inherits Atlassian's data residency controls
• Never leaves Atlassian's infrastructure
• Is isolated per Jira site

Yes. TeamOps includes built-in GDPR tools:

• Right of Access: HR Admins can export all data for any employee.
• Right to Erasure: HR Admins can permanently delete all data for an employee.
• Data Minimization: Only necessary data is stored.
• Audit Trail: All exports and deletions are logged.

See our Privacy Policy for full details.

• You can see all your own requests.
• Your manager can see your requests (since they approve them).
• HR Admins can see all requests across the organization.
• Other employees can see on the calendar that you are out, but not the details (leave type, notes).

Yes. HR Admins can export all data for a specific employee (profile, leave history, balances, onboarding records) via Settings > GDPR & Privacy > Export Employee Data.

Yes. TeamOps is free for up to 10 users with core features included -- onboarding, offboarding, leave management, employee directory, and the dashboard gadget. No time limit.

Pricing is based on the number of Jira users on your site:

The Pro tier includes unlimited custom templates, full leave history, advanced analytics, and priority support. Billing is handled through the Atlassian Marketplace.

No. Atlassian Marketplace apps include a free evaluation period (usually 30 days) during which you can try the full app without being charged.

TeamOps will prompt your Jira administrator to upgrade to the Pro tier. The app continues to work during a grace period so there is no disruption.

• Make sure the app has been installed by your Jira site administrator.
• Try refreshing your browser or clearing your cache.
• Check that you have permission to access apps on your Jira site.

Your HR Admin can fix this in TeamOps Settings > Holidays. Verify the correct country is selected, then add, remove, or edit individual holidays as needed.

• Ask your manager to check their Jira notification bell.
• Confirm your manager is set as your manager in TeamOps (your HR Admin can verify this).
• Check that leave notifications are enabled in TeamOps Settings > Notifications.
• Verify your manager's Jira notification preferences allow email delivery.

• Pending requests reduce your displayed "Available" balance even though they have not been approved yet.
• If your HR Admin recently changed your allocation, the balance updates immediately.
• Check your leave history for any requests you may have forgotten about.
• Contact your HR Admin if the numbers still do not match your expectation.

HR Admins can start an offboarding by going to TeamOps HR Portal > Offboarding > Start Offboarding. Select the departing employee, choose an offboarding template, and enter their last day. Tasks are created and assigned automatically.

Offboarding completion does not delete employee data. Their leave history, onboarding records, and profile remain in TeamOps for compliance and audit purposes. HR Admins can use the GDPR data erasure feature to permanently delete all records when appropriate.

Yes. Offboarding templates work the same way as onboarding templates. You can create role-specific templates with tasks like equipment return, access revocation, exit interviews, and knowledge transfer — each assigned to the appropriate department.

Offboarding tasks are structured around the employee's last day rather than their start date. Phases typically include "Before Last Day" (knowledge transfer, project handoff), "Last Day" (equipment return, access revocation), and "After Departure" (final payroll, benefit termination, exit interview follow-up).