Data handling

Last updated: July 1, 2026

Does the Jira app require an external backend?

No external application backend is required for normal Jira Cloud app operation. Cloud Scheduler is presented as a Forge-native app using Atlassian-hosted runtime and Forge Storage.

Jira data read by the app

• Jira project identifiers and project names required for planning context.
• Jira issue identifiers, issue keys and issue summaries.
• Issue statuses, priorities, issue types and labels.
• Assignee/account identifiers and display information needed for resource planning.
• Jira groups where group-based resource planning is used.
• Worklog metadata required for planned-versus-logged analysis.
• Dates, estimates or planning-related issue metadata when available and permitted by Jira scopes.

Data stored

• Cloud Scheduler groups and resource structure.
• Planning entries linked to Jira work items.
• Planned dates, planned hours and resource assignments.
• Planning notes, colors, visual metadata and display preferences.

Website contact data

The contact page does not use a web form. Users contact the team directly by email. Any support information is handled through the official mailbox support@cloudschedulerapp.com.