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)
ASSETS
Icons (both)
Global (both)
Image (both)
Name (both)
Object Icons (both)
Objects (both)
Activity (both)
Attachments (both)
Comments (both)
Default Type Attribute Value (both)
Group Type Attribute Value (both)
Linked Issues (both)
Linked Objects (both)
Object Type Attribute Value (both)
Original ID (both)
Project Type Attribute Value (both)
Status Type Attribute Value (both)
User Type Attribute Value (both)
Object Types (both)
Abstract Setting (both)
Children Type (both)
Description (both)
Icon (both)
Name (both)
Parent Type (both)
Pass all attributes to child object types (both)
Roles (both)
Reference Types (both)
Color (both)
Description (both)
Global (both)
Name (both)
Per scheme (both)
Roles (both)
Object Schema Developers - Groups (both)
Object Schema Developers - Users (both)
Object Schema Managers - Groups (both)
Object Schema Managers - Users (both)
Object Schema Users - Groups (both)
Object Schema Users - Users (both)
Object Viewers - Groups (both)
Object Viewers - Users (both)
Roles per Object Type (both)
Roles per Schema (both)
Schema (both)
Allow others to select objects from this schema (both)
Description (both)
Enable quick creation of referenced objects (both)
Key (both)
Name (both)
Validate objects attributes in quick object creation (both)
Statuses (both)
Category (both)
Description (both)
Global (both)
Name (both)
Per Scheme (both)
AUTOMATION RULES
Description (both)
Enabled (both)
Flow (Triggers, Actions, Conditions) (both)
Name (both)
Notify on error (both)
Owner (both)
Who can edit this rule? (both)
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)
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 (WORK ITEMS)
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 (WORK ITEM) TYPE SCREEN SCHEMES
Description (classic)
Issue type to screen scheme mapping (classic)
Name (classic)
ISSUE (WORK ITEM) 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)
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)
Last updated
Was this helpful?

