ES EN

Documentation

ClockIn for Jira is a working-time tracking app for Jira Cloud. This page covers installation, first steps, core features, configuration, and frequently asked questions.

1. Installation

ClockIn for Jira is distributed through the Atlassian Marketplace and installs directly into your Jira Cloud site.

• Go to the Atlassian Marketplace and search for "ClockIn for Jira".
• Click Get it now and choose the Jira Cloud site where you want to install the app.
• Confirm the requested permissions and complete the installation.
• Only Jira site administrators can install or uninstall apps. If you don't have admin access, ask your Jira administrator to install it on your behalf.

Once installed, the app appears in the Jira navigation as ClockIn and is available to every user on the site.

2. Getting started

To log your first clock-in session:

• Open the ClockIn item from the Jira navigation.
• Click Start to begin tracking your working time.
• The app records the timestamp automatically — there is nothing else to configure to start using it.
• When you finish your session, click Stop. Your recorded time is saved to your personal history.

If your organization has configured a company work schedule, ClockIn compares your logged time against it and flags any mismatches.

3. Core features

Start / Pause / Resume / Stop

Clock events follow a simple state machine:

• Start — begins a new working session.
• Pause — stops the clock temporarily, for example during a break.
• Resume — continues a paused session.
• Stop — ends the session and closes the record for that day.

Every event is timestamped and kept as an immutable record, forming the basis of your time-tracking history.

Team view

Managers and admins can see the status and logged hours of their team members from a dedicated team view, useful for monitoring attendance and spotting incidents without leaving Jira.

Incidents

If a clock event is missing or incorrect, users can raise an incident to request a correction. Managers can review and resolve incidents, keeping a clear audit trail of any changes to the original record.

Export

Time records can be exported in CSV format for payroll, audits, or compliance purposes. Exports can be filtered by user, team, or date range, depending on your role.

4. Configuration

Administrators configure the app from the ClockIn settings panel:

• Company work schedule — define expected working hours per day or week, used to flag deviations in employee records.
• Roles — assign each user a role of employee, manager, or admin, controlling what they can see and do within the app.
• Timezone — set the timezone used to timestamp and display clock events, ensuring consistency across distributed teams.

5. Frequently asked questions

Do I need a separate account to use ClockIn?

No. ClockIn uses your existing Atlassian account — there is no separate sign-up or login.

Can I edit a clock event after it's been recorded?

Clock events are immutable. To fix a mistake, raise an incident instead, which creates a reviewable correction without altering the original record.

Who can see my time records?

You can always see your own records. Managers and admins in your organization can see records according to the role configuration set by your administrator.

How much does ClockIn cost?

ClockIn is a paid app, with tiered per-user pricing based on your organization's size, managed through the Atlassian Marketplace. See the app listing on the Marketplace for current pricing.

What happens to my data if the app is uninstalled?

Data stored by the app is removed in accordance with Atlassian Forge's data retention policies following uninstallation. See our Privacy Policy for details.

Where can I get support?

See our Support page for contact channels, support hours, and what to include in a request.