Cloud Scheduler
ContactReviewer guide

Atlassian reviewer guide

This guide is intended for Atlassian Marketplace reviewers validating a new Cloud Scheduler listing. The goal is to provide a clear, repeatable path to verify that the app performs as described, respects Jira context, and exposes relevant customer-facing documentation.

Installation and access model

  • Cloud Scheduler is intended for Jira Cloud and is presented as an Atlassian Forge app.
  • After installation, a Jira administrator or authorized user opens a Jira project with sample issues.
  • In the project or board context, the user can use the app entry point or plus/add option to display Cloud Scheduler when available in the Jira UI.
  • The app should then be usable in a simple planning workflow: define resources, create planning entries linked to Jira issues, review schedules, then validate timelines and execution indicators.

Reviewer prerequisites

  • A Jira Cloud test site where Marketplace app installation is allowed.
  • One Jira administrator account for installation and configuration checks.
  • One standard Jira user account for permission and access validation.
  • One Jira project with sample issues, different statuses and assigned users.
  • At least one board where a reviewer can validate the app access path from the project or board area.
  • Optional Jira groups and sample worklogs to validate resource and timesheet behavior.

Suggested validation flow

  1. Install Cloud Scheduler on the Jira Cloud test site using an administrator account.
  2. Open a Jira project that contains sample issues and users.
  3. From the project or board area, use the app entry point or plus/add option to display Cloud Scheduler in the project context when available.
  4. Open Resource and add Jira resources, Jira groups, generic resources or Cloud Scheduler groups.
  5. Create planning entries or tasks in Schedule and link them to Jira issues or Jira work items.
  6. Assign planned work to a resource, dates and planned hours.
  7. Open Calendar to validate monthly visibility of planned work, holidays, events and availability.
  8. Open Gantt to validate roadmap/timeline planning for planned work over time.
  9. Open Timesheet to compare planned effort with Jira logged work when sample worklogs exist.
  10. Open Pulse to review workload, capacity and planning health indicators.

Functional areas to validate

  • Resource: verify that Jira users, Jira groups, generic resources or Cloud Scheduler groups can be represented for planning.
  • Schedule: verify that planning tasks or entries can be created and associated with Jira issues or Jira work items.
  • Calendar: verify monthly planning visibility and date-based readability.
  • Gantt: verify timeline planning, roadmap readability and portfolio-style visibility.
  • Timesheet: verify planned-versus-logged follow-up when Jira worklogs are available.
  • Pulse: verify dashboard-level workload and planning indicators.

Expected reviewer observations

  • The app should not break the Jira user interface.
  • The app should perform consistently with the public documentation and Marketplace listing.
  • The documented scopes should align with the app manifest and Marketplace Privacy & Security tab.
  • The public support, security, privacy, data handling, EULA and terms pages should be accessible.
  • The app should not ask users for Atlassian login credentials or passwords.
  • If a feature requires Jira permissions, access should follow Jira permission boundaries.

Support during review

support@cloudschedulerapp.com