Admin Hardening Guide

Cloud This page documents the Forge build of Time in Status for Jira Cloud. On Jira Data Center or Server? See Time in status | SLA | Timer | Stopwatch for Data Center.

Audience and purpose

This guide is for the Jira site administrator who installs Time in Status for Jira Cloud (Forge) (or inherits an existing installation) and needs to confirm that the configuration is production-ready. It does not replace the per-feature reference docs - it walks you through them in the right order, with the safest defaults flagged.

Read this once during install, then return to the Ongoing checklist on a monthly cadence. For a high-level view of what scopes the app requests, see the Permissions Reference. For a security review or DPIA, see the Security Reference for Auditors.


At a glance: secure-by-default

Time in Status (Forge) ships with conservative defaults. Most are safe to keep; a few are opt-in by intention.

Setting Default Notes
Admin page access Site admins only Gated by Forge user_is_admin condition; re-checked server-side on every mutating resolver call
Per-project panel visibility Hidden until explicitly enabled The four panels (Time in Status, Stopwatch, Timer, Activity) render only in projects where the tis-cloud-panels project property opts them in. See Panel visibility
Field-context scoping No contexts until a Jira admin assigns one Each app-owned custom field is registered in Jira’s field configuration; the app processes only the projects and issue types where the field has a context. Adding a field-context is a Jira admin action
Outbound network None except the weekly account-ID report The app declares no external: scopes; the only endpoint outside your Jira site is Atlassian’s Personal Data Reporting API
Forge platform encryption At rest, Forge-managed Configurations and metric values stored in Forge SQL (MySQL) and Forge KV; transport is HTTPS via Forge ingress
Recalculation queue Async; bounded Bulk recalculations are processed by the tis-async-consumer queue with a 180-second per-message timeout
Diagnostic logging Error level only in production Custom logger redacts accountId, email, display name, JWT patterns; debug/info suppressed in production
Personal data stored Atlassian accountId of the administrator who starts a bulk recalculation, and of people picked in Count only while conditions on user fields Job initiator - kept with the job record for 30 days; condition values - kept in the field setting until the condition is changed. Both are reported weekly to Atlassian Personal Data Reporting and removed when the account is closed. Configuration items carry no creator or updater attribution
JSM portal exposure None The app does not register any JSM portal modules and has no unlicensedAccess surface
Rovo agents None The app does not declare read:chat:rovo and registers no rovo:agent modules

Day 0: pre-install considerations

Before clicking Install on the Marketplace listing:

  • Review the Permissions Reference and the scope prompt that Jira will show during install.
  • Coordinate with your DPO or privacy officer using the DPA.
  • Decide who in your organization will hold Time in Status admin access. Time in Status admin = Jira site admin - there is no separate role.
  • If you are migrating from the legacy Connect app (com.jibrok.jira.plugins.time-in-status), plan the upgrade window. Connect → Forge is an in-place Marketplace update on the same site - JCMA is not involved and the upgrade cannot be rolled back, so export the Connect configuration to JSON first. See Migration from Connect to Forge.
  • If you are migrating from Jira Data Center, plan the JCMA migration window instead - the Data Center app delivers its configuration to the Forge app through Atlassian’s Jira Cloud Migration Assistant. See Migration from Data Center to Forge Cloud.
  • If you run separate Jira sites for testing and production, install the app on each and validate configuration changes on the test site first.
  • If your organization also uses the separate Timer field, Stopwatch field or Time between dates listings, decide which listing will own each field type before installing: the unified Time in Status / SLA / Timer / Stopwatch listing already includes all of them, and two listings tracking the same field type on one site duplicate processing on those issues.

Day 1: post-install checklist

Walk through these in order on the day you install Time in Status (Forge). Most checks take less than 5 minutes each.

  • Verify install context. Open Apps -> Manage your apps -> Time in Status in Jira and confirm the version, Marketplace listing source, and installer match what you expect.
  • Open the admin panel. From Apps -> Manage your apps -> Time in Status -> Configure. The page loads within a few seconds; if it does not, see Troubleshooting. Confirm that you (an admin) can see all 11 tabs - Time in Status, Stopwatch, Timer, Time Between Dates, Custom Events, Activity Panels, Calendars, Recalculation, Import / Export, Health Check and Backups - per Admin panel overview.
  • Confirm panel visibility is locked down. Go to Panel visibility and confirm no project has panels enabled by default. Add panels project-by-project as use cases are validated. See Panel visibility.
  • Configure your first field with the smallest possible context. Create the first Time in Status (or whichever field type you need) and assign it a Jira field-context that covers exactly one pilot project and one issue type. Confirm you see calculated values appear in the issue view within a few minutes. See Time in Status field create.
  • Set up at least one work calendar that matches your business hours. The built-in 24x7 calendar is always available, but most production deployments need a working-hours calendar. See Work calendars.
  • Personal-data reporting needs no action. It runs from the weekly personal-data-report scheduled trigger, which submits the stored account IDs to Atlassian’s Personal Data Reporting API and applies the erase and refresh actions Atlassian returns.
  • Document who has Jira admin access. Anyone with Jira site admin can manage Time in Status. Treat the Jira admin list as the Time in Status admin list.
  • Document your escalation paths. Who responds to a security incident? Who handles license expiry? Both are admin-only events.

If you are migrating from Connect:

  • Export the Connect configuration to JSON before the Marketplace update and rehearse the import on a non-production site if you have one; the update replaces the Connect build in place and cannot be rolled back. See Migration from Connect to Forge.

If you are migrating from Data Center:

  • Stage the JCMA migration on a non-production Cloud site first. Run the full cycle - upload through Atlassian’s Jira Cloud Migration Assistant, background import, verification of the imported configurations - before the production window. See Migration from Data Center to Forge Cloud.

In both cases:

  • Plan a recalculation window after migration. Migration transfers configuration only; per-issue values are recalculated from issue history, so run a full recalculation for each migrated field context. See Recalculation.

Week 1: first-week monitoring

Once Time in Status (Forge) is running:

  • Sample-check rendered panels in production projects. Open issues across the projects where you enabled panels and confirm the displayed metrics look correct (status durations match Jira changelog, work-calendar hours are respected, custom events fire as expected).
  • Watch the Recalculation tab. Look for stuck jobs, repeated errors, or unusual durations. The async consumer has a 180-second per-message timeout; messages that hit the timeout are retried per the Forge platform retry policy.
  • Confirm values keep updating. If calculated values stop changing in a project, check the Recalculation tab for failed jobs and confirm the field context still covers that project and that its JQL filter still parses.
  • Confirm field-context coverage matches intent. Open Jira admin -> Custom fields for each app-owned custom field and confirm its contexts cover only the projects and issue types you intended.

Ongoing: monthly checklist

Schedule a recurring 30-minute review:

  • Audit field-context coverage. Remove projects and issue types from field contexts where the field is no longer needed. Each context expansion increases the recalculation surface and the app’s read footprint on issue data.
  • Audit panel visibility. If a project no longer needs Time in Status, Stopwatch, Timer, or Activity panels, turn them off for that project in Panel visibility. The fewer projects opted in, the smaller the rendering surface.
  • Audit work calendars. Remove unused calendars; check that calendars used in production reflect current holidays and business hours.
  • Audit custom events. If a custom event no longer triggers, remove it. Custom events are evaluated on every issue/comment update; unused events still cost evaluation time.
  • Confirm license is active. When Jira reports the app license as inactive, the app stops recalculating and writing field values - on issue events, in background sweeps and in batch recalculation. Values already on issues stay, and issue panels, the Activity panel, JQL searches by values and the Calendar Select field keep working. The admin and field context configuration pages show This app requires an active license. Check the app license in Manage apps. Renew before expiry; after renewal, run a full recalculation - the app does not catch up on its own.
  • Review the Recalculation history. Investigate any failed jobs; if a project consistently fails to recalculate, check its workflow for unusual states or its custom-field schema.

Recalculation playbook

Recalculation is the primary admin-controlled bulk operation. Use it after:

  • A field configuration change that affects how time is computed (for example, adding/removing statuses from a Time in Status field setting, changing the work calendar).
  • A migration from Connect (one full recalculation per migrated field-context).
  • A historical changelog correction (an admin manually edits past statuses on bulk issues).

Recommended posture:

  • Scope tightly. Always recalculate by project + field-context + issue range. A blanket “all projects” recalculation can take hours and saturate the queue.
  • Off-hours. Schedule large recalculations outside working hours so that event-driven updates stay responsive.
  • Monitor. Watch the Recalculation tab for queue depth and per-job status. Use the Cancel action if a misconfigured job needs to be stopped.
  • One at a time. Avoid starting multiple bulk recalculations in parallel; the queue is shared.

For the feature reference, see Recalculation.


Migration specifics

From Connect (Jira Cloud). The Forge app declares the Connect app key com.jibrok.jira.plugins.time-in-status, so the Marketplace update replaces the Connect build in place on the same Jira Cloud site. Configuration travels as a JSON export from the Connect admin page and is imported through Import / Export in the Forge admin page; JCMA is not involved, and the update cannot be rolled back. See Migration from Connect to Forge.

From Data Center. Atlassian’s Jira Cloud Migration Assistant (JCMA) uploads the Data Center app’s configuration to the Forge app through the Forge migration event. The app imports it in the background and reports the result back to JCMA; ordinary event handling continues during the window. Per-issue values are not copied - run a full recalculation afterwards. See Migration from Data Center to Forge Cloud.

In both cases, verify migrated configurations by sampling a few projects once the import completes, then recalculate each migrated field context.

For step-by-step migration guidance, start from Migration to Time in Status (Forge) and follow the route that matches your source - Data Center or Connect.


CSP relaxation note

The manifest declares permissions.content.styles: ['unsafe-inline']. This is a Forge content-rule directive that allows the admin page (a Custom UI whose component library emits inline styles) to apply those styles. The directive applies only to the admin-page resource; it does not relax CSP for the issue-panel or field-context-config resources (which are Forge UI Kit components rendered server-side) and it does not enable script execution, network egress, or DOM access beyond the admin iframe.

There is no admin action required for this directive; it is documented here so security review knows what it is and why.


Incident response quick reference

If you suspect the app is misbehaving or your installation is compromised:

Action Where
Hide a single panel project-wide Turn the panel off for that project in Panel visibility - the panel disappears immediately
Hide all panels globally In Panel visibility, turn every panel type off at app level and clear any project-level overrides - panels stop rendering everywhere within seconds
Disable a single custom field Remove the field-context from the affected projects via Jira admin - the app stops processing issues in those projects on the next event tick
Stop recalculation Cancel running recalculation jobs from the Recalculation tab; no new messages are queued and in-flight messages finish
Export configurations for forensics Use Import / export configurations to export all configurations as JSON; preserve the export alongside an incident record
Uninstall the app Standard Atlassian app uninstall. Forge deletes the app’s data per the DPA section 8.3. The app’s custom fields are removed from Jira together with the app, so the values stored in them are no longer available after uninstall - export configurations first if you may reinstall
Report a vulnerability Use the Vulnerability Disclosure channel or contact security@jibrok.com

Other security docs