Zabezpieczone zasoby

Lista zabezpieczanych zasobów Jira.

Zabezpieczone zasoby Jira definiują, do których części środowiska Jira Xopero ONE ma dostęp oraz które z nich może zabezpieczać i przywracać.

---

Zabezpieczone dane

Poniższa lista została przedstawiona w porządku alfabetycznym.

Legenda:

• classic — chronione tylko w projektach klasycznych (classic projects).

• next-gen — chronione tylko w projektach nowej generacji (next-gen projects).

• both — chronione zarówno w projektach klasycznych, jak i nowej generacji.

BOARDS

• Admins (classic)

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

• Board Filter (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)

• Project relation (classic)

• Quick Filters (both)

• 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)

PROJECT ROLES

• Default Role Actors (classic)

• Description (both)

• Inner Project Actors - Groups (both)

• Name (both)

• Permissions (project scoped) (next-gen)

PROJECTS

• Assignee Type (both)

• Description (both)

• Features (both)

• Key (both)

• Lead (both)

• Name (both)

• Type (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)

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)