Protected resources

List of protected Jira resources.

Jira protected resources define which parts of your Jira environment Xopero ONE can access, secure, and restore.

---

Protected data

The following list is presented in alphabetical order.

🔑 Key definitions:

• classic — data protection available only for classic spaces (projects)

• next-gen — data protection available only for next-gen spaces (projects)

• both — data protection available for both classic and next-gen spaces (projects)

AUTOMATION RULES

• Description

• Enabled

• Flow (Triggers, Actions, Conditions)

• Name

• Notify on error

• Owner

• Who can edit this rule?

BOARDS

• Admins (classic)

• Are card cover images allowed? (next-gen)

• Board filters (classic)

• Card config - active sprints fields (classic)

• Columns - max (both)

• Columns - min (classic)

• Columns - name (both)

• Columns - status (both)

• Completed work items cutoff (classic)

• Name (both)

• Non-working dates (classic)

• Quick filters (both)

• Project relation (classic)

• Region (classic)

• Show days in column (classic)

• Swimlane - Description (classic)

• Swimlane - Name (classic)

• Swimlane - Position (classic)

• Swimlane - Query (classic)

• Swimlane method (classic)

• Timeline - are child-level work items included? (classic)

• Timeline - child work item scheduling (next-gen)

• Timeline - is enabled? (classic)

• Timezone (classic)

• Type (classic)

• Working days (classic)

COMPONENTS

• Assignee Type (both)

• Description (both)

• Lead (both)

• Name (both)

• Project relation (both)

FIELD CONFIGURATION

• Description (both)

• Field configuration item - Description (both)

• Field configuration item - Hidden Status (both)

• Field configuration item - Issue Relation (both)

• Field configuration item - Renderer (both)

• Field configuration item - Require Status (both)

• Name (both)

FIELD CONFIGURATION SCHEMES

• Description (both)

• Name (both)

• Project relation (both)

• Relation between issue type and field configuration (both)

FIELDS

• Description (classic)

• Global field (both)

• Name (classic)

• Options (classic)

• Project scoped field (next-gen)

• Searcher key (classic)

• Type (classic)

ISSUES

• Assignee (both)

• Attachments (both)

• Comments (both)

• Components (both)

• Description (both)

• Fix Versions (both)

• Other fields (both)

• Parent (both)

• Priority (both)

• Project (both)

• Status (both)

• Summary (both)

• Type (both)

• Value for option type fields (both)

• Value for Service Desk request type fields (both)

• Value for team type fields (both)

• Value for user type fields (both)

ISSUE LINK TYPES

• Inward description (both)

• Name (both)

• Outward description (both)

ISSUE TYPE SCREEN SCHEMES

• Description (classic)

• Issue type to screen scheme mapping (classic)

• Name (classic)

ISSUE TYPE SCHEMES

• Default issue type relation (classic)

• Description (classic)

• Field default values (next-gen)

• Field positions (next-gen)

• Field relations (next-gen)

• Field required status (next-gen)

• Field section (next-gen)

• Global fields relations (next-gen)

• Issue types relations (next-gen)

• Name (classic)

• Other issue types relations (classic)

• Project scoped field options (next-gen)

ISSUE TYPES

• Avatar (both)

• Description (both)

• Hierarchy level (both)

• Name (both)

ISSUE COMMENTS

• Attachments (both)

• Content (both)

• Is internal (both)

• Parent relation (both)

NOTIFICATION SCHEMES

• Description (classic)

• Event receiver (both)

• Event type (both)

• Name (classic)

• Project relation (both)

SCREEN

• Description (classic)

• Name (classic)

• Tab - fields relations (classic)

• Tab - name (classic)

• Tabs (classic)

SCREEN SCHEMES

• Description (classic)

• Name (classic)

• Operation to screen mapping (classic)

• Tabs (classic)

• Tab (name) (classic)

• Tab (fields relations) (classic)

SPACES (PROJECTS)

• Assignee Type (both)

• Description (both)

• Features (both)

• Key (both)

• Lead (both)

• Name (both)

• Type (both)

SPACE (PROJECT) ROLES

• Default Role Actors (classic)

• Description (both)

• Inner Project Actors - groups (both)

• Name (both)

• Permissions - project scoped (next-gen)

SPRINTS

• Board relation (both)

• Complete date (both)

• End date (both)

• Goal (both)

• Issue relation (both)

• Name (both)

• Start date (both)

• State (both)

VERSION

• Description (both)

• Name (both)

• Project relation (both)

• Release date (both)

• Start date (both)

• Status (unreleased/archived/released) (both)

WORKFLOWS

• Description (both)

• Name (both)

• Starting point (both)

• Statuses (both)

• Transitions (both)

WORKFLOW SCHEMES

• Default workflow mapping (classic)

• Description (both)

• Issue type workflow mapping (both)

• Name (both)

• Project relation (both)