Configuration Object Support Matrix
- Rosen Marinkov
- Stanley Neychev
- Julver Petrova (Deactivated)
Â
Supported configuration objects
The table below shows the full list of supported configuration objects. Additionally, to find information about 3rd party apps integrated with Configuration Manager, see the List of Integrated Apps document.
 | Configuration Object | Root Object | Since | Notes |
|---|---|---|---|---|
 | Project | Â | Â | Â |
 | Project | root | 1.0.0 | Â |
Component | child | 1.0.0 | ||
Version | child | 1.0.0 | ||
Category | root | 1.0.0 | Â | |
Workflows | Â | Â | Â | |
Workflow | root | 1.0.0 | ||
Workflow Scheme | root | 1.0.0 | ||
Fields | Â | Â | Â | |
Custom field | root | 1.0.0 | ||
Custom field context | child | 1.0.0 | ||
Field configurations | root | 1.0.0 | Â | |
Field Configuration Schemes | root | 1.0.0 | ||
Screens | Â | Â | Â | |
Screen | root | 1.0.0 | Â | |
Screen Scheme | root | 1.0.0 | Â | |
Issue Type Screen Scheme | root | 1.0.0 | ||
| Â | Â | Â | |
Issue Type | root | 1.0.0 | Â | |
Issue Type Scheme | root | 1.0.0 | Â | |
Sub-Tasks | root | 1.0.0 | Â | |
Resolution | root | 1.0.0 | Â | |
Priority | root | 1.0.0 | Â | |
Status | root | 1.0.0 | Â | |
Permissions & Security | Â | Â | Â | |
Global Permissions | root | 1.0.0 | Â | |
Permission Schemes | root | 1.0.0 | Â | |
Issue Security Schemes | root | 1.0.0 | Â | |
User management | Â | Â | Â | |
Users | root | 1.0.0 | ||
Roles | root | 1.0.0 | Â | |
Groups | root | 1.0.0 | ||
Notifications | Â | Â | Â | |
Notification Schemes | root | 1.0.0 | Â | |
Events | root | 1.0.0 | Â | |
 | Filters & Dashboards |  |  |  |
 | Filters | root | 3.0 | |
 | Dashboards | root | 4.1 | |
 | Agile |  |  |  |
 | Agile Boards | root | 4.0 | |
 | Agile Sprints | root | 4.0 |  |
Jira Service Management | Â child | 6.0 | Â | |
 | Portal settings | child | 6.0 |  |
 | Feedback settings | child | 6.0 |  |
 | Participant management | child | 6.0 |  |
 | SD access configuration | child | 6.0 |  |
 | Email channel | child | 6.0 |  |
 | Queues | child | 6.0 |  |
 | Calendars, holidays, working times | child | 6.0 |  |
 | Goals | child | 6.0 |  |
 | Time metrics (SLAs) | child | 6.0 |  |
 | Request types | child | 6.0 |  |
 | Request type groups | child | 6.0 |  |
 | Request type fields | child | 6.0 |  |
 | Request type statuses | child | 6.0 |  |
 | Reports and series | child | 6.0 |  |
 | Customer notification settings | child | 6.0 |  |
 | Outgoing email settings | child | 6.0 |  |
 | Languages | child | 6.0 |  |
 | Default notification rules | child | 6.0 |  |
 | Knowledge base | child | 6.0 |  |
 | Automation rules and all related configuration | child | 6.0 |  |
 | Organizations | root | 6.0 | |
 | Organization members | child | 6.0 | |
 | Other |  |  |  |
 | Issue Link Types | root | 1.2.1 |  |
Root Configuration Objects
Knowing which objects are considered root configuration objects will help you better understand the process of creating and deploying snapshots. That’s because when deploying a snapshot with CMJ, you’ll only be given differences between root objects to review.
Root configuration objects contain child configuration objects within them. So, by understanding which objects are ROOT and CHILD, you can make better judgments when deciding which ones to keep and which to merge.
Root and child objects
Examples of root configuration objects are project, workflow, issue type, etc.
Examples of child configuration objects are version, component, post-function, condition, etc.
Â