Privacy notice: Parent & Child Fields for Jira

Effective 2026-09-21. Publisher: Sidecar Tools (support@sidecartools.com).

What the app reads. For each work item: its parent, status, assignee, issue type and sub-task list, plus the status of its child work items and the site's field list, using the read:jira-work scope. It does not read summaries, descriptions, comments or attachments.

What the app writes. Six app-owned custom field values on work items (write:app-data:jira): Child count, Open child count, Child progress %, Parent status, Parent status category, and Parent assignee (the parent assignee's account id).

Where data lives. Entirely inside your Atlassian site. Field values are stored by Jira as issue fields. The app stores only its own field ids and a backfill timestamp in Forge Key-Value Storage (storage:app). Nothing is sent outside Atlassian's infrastructure; the app has no external egress and no servers of its own. The app does not log field values, status names or account ids.

Who can see the fields. The same people who can see the work item that carries them. Note: "Parent status", "Parent status category" and "Parent assignee" are fields on the child and follow the child's permissions. If a parent is hidden from some users by an issue security level or lives in a project they cannot browse, while its children are visible to them, those users can see the parent's status and assignee on the child. If that matters for your site, hide the three parent fields from the screens and filters those users work with.

Retention. Values remain on work items until the app is uninstalled; uninstalling removes the fields and their values per Jira's handling of app-owned fields.

Analytics and tracking. None.

Contact. support@sidecartools.com.