Documentation
This page explains how to install, open, and test SentinelTime AI on Jira Cloud. Use it as the Marketplace documentation link for reviewers and customers.
Contents
- Overview
- Requirements
- Install from Marketplace
- Open the app
- First-run checklist
- Reviewer test plan
- Main features
- Permissions
- Data & security
- Support
Overview
SentinelTime AI is a Forge-native Jira Cloud app for fast worklog entry, weekly timesheets, team capacity, project reporting, and optional writing assistance. The Marketplace build authenticates through Atlassian Forge. It does not ask customers for Atlassian API tokens.
Requirements
- Jira Cloud site with permission to install Marketplace apps
- A Jira user who can browse issues and create worklogs on those issues
- Modern desktop browser (Chrome, Edge, Firefox, or Safari)
- Optional: team/admin role inside the app for approval and team views
Install from Marketplace
- Open the SentinelTime AI listing on Atlassian Marketplace, or use Apps → Explore more apps in Jira Cloud and search for SentinelTime AI.
- Select your Jira Cloud site and start the free trial / purchase flow managed by Atlassian.
- Approve the app permissions when prompted. The app requests only the scopes required for worklogs, user display, and Forge remote processing.
- Wait for installation to complete. Forge installs the global page and issue-context modules automatically.
For Marketplace reviewers: Install on a non-production Jira Cloud test site. No customer API token setup is required. Authentication and licensing are handled by Forge and Atlassian.
Open the app
Global workspace
- In Jira Cloud, open the Apps menu (or the app switcher, depending on your Jira UI).
- Select SentinelTime AI.
- The workspace loads as a Custom UI page. Your Atlassian identity is provided by Forge; no separate login is required inside the Marketplace build.
Issue panel
- Open any Jira work item (issue).
- Find the SentinelTime AI issue context / panel module.
- Use it to log time against the current issue without leaving the issue view.
First-run checklist
- Confirm the workspace opens without an API-token form.
- Search for an issue you can edit worklogs on.
- Create a short test worklog (for example 15 minutes) and confirm it appears on the issue in Jira.
- Edit or delete that worklog from the app and verify the change in Jira.
- Optionally open Team / Reports views if your role allows them.
Reviewer test plan
Use this sequence when validating the Marketplace listing:
- Install: Install SentinelTime AI on a Jira Cloud site and accept scopes.
- Open: Launch the global page from the Apps menu.
- Create worklog: Search an issue, enter duration and description, submit, and confirm the worklog in Jira.
- Edit / delete: Change duration or description, then delete the test entry.
- Issue panel: Open a work item and log time from the issue context module.
- Timesheet: Review daily/weekly views and, if available, submit a period for approval.
- Team / reports (optional): Open team capacity or export a report if your test user has access.
- Uninstall / reinstall (optional): Remove the app and reinstall to confirm clean recovery of the Forge install path.
Expected security behavior: Remote API calls are authenticated with Forge Invocation Tokens. Missing or invalid tokens are rejected. Tenant data is isolated per installation/workspace. Optional AI assistance is reviewable before any Jira write.
Main features
- Daily worklog workspace — search issues, enter time, refine descriptions, and submit without multi-screen navigation.
- Weekly timesheets — track progress against daily targets and prepare review-ready periods.
- Approvals — submit weekly/monthly periods to a lead; decided periods can be locked against later edits.
- Team capacity — view logged hours, missing entries, leave, and project distribution for the current Jira site.
- Reports — filter by person, project, or customer; export Excel/PDF; share expiring read-only links when enabled.
- Budgets — issue/project budget alerts at 80% and 100% thresholds.
- Assistance — optional description improvement and summaries; users review results before they are written to Jira.
- Excel import/export — move worklog data in bulk when needed.
Permissions
Typical Forge scopes used by the app:
read:jira-work— read issues, projects, and worklogs selected by the userwrite:jira-work— create, update, and delete worklogs after an explicit user actionread:jira-user— show names and avatars in team viewsread:app-user-token/read:app-system-token— call Jira from the declared Forge Remote with short-lived tokensreport:personal-data— report retained account identifiers and erase closed or updated accounts per Atlassian privacy requirements
Data & security
- The Marketplace app runs on Atlassian Forge Custom UI with a declared Forge Remote.
- Customer Atlassian API tokens are not requested or stored by the Forge Marketplace app.
- Workspace data is tenant-scoped with server-side authorization and database Row Level Security.
- Privacy, security, and terms documents:
Privacy Policy · Security Policy · Data Processing Agreement · Terms / EULA
Support
For installation problems, unexpected worklog behavior, privacy requests, or security reports, use the support page. Include your Jira site URL, approximate time of the issue, and a screenshot with sensitive data removed.
Open support