Jira Service Management Field Configuration Scheme for Project CM
Different issues can have different information fields. A field configuration defines how fields behave for the project, e.g. required/optional; hidden/visible.
The field configuration scheme defines which fields apply to this project. To change the fields used, you can select a different field configuration scheme, or modify the currently selected scheme.
This project uses only 1 field configuration.
These 8 issue types…
-
[System] Change
-
[System] Incident
-
[System] Post-incident review
-
[System] Problem
-
[System] Service request
-
[System] Service request with approvals
-
Task
-
Sub-task
…use this field configuration
| Name | Required | Renderers | Screens |
|---|---|---|---|
|
Actual Finish
|
1 screen | ||
|
Actual Start
|
1 screen | ||
|
Actual end
Enter when the change actually ended. |
3 screens | ||
|
Actual start
Enter when the change actually started. |
3 screens | ||
|
Affected Environments
Affected environment (Android, iOS, etc) |
1 screen | ||
|
Affected hardware
|
Default Text Renderer | 3 screens | |
|
Affected services
Locked
Link services from the service registry to an issue. |
11 screens | ||
|
Affects versions
|
4 screens | ||
|
Approvals
Locked
Provides search options for Jira Service Management approvals information. This custom field is created programmatically and required by Jira Service Management. |
No screens | ||
|
Approver groups
Contains groups of users needed for approval. This custom field was created by Jira Service Management. |
11 screens | ||
|
Approvers
Contains users needed for approval. This custom field was created by Jira Service Desk. |
12 screens | ||
|
Are all UI and Live Integrations towards backend fully tested?
Did you test your feature from start to finish? Did you test all integrations to make sure everything is working correctly? |
No screens | ||
|
Assignee
|
34 screens | ||
|
Attachment
|
21 screens | ||
|
Backout plan
|
Default Text Renderer | 3 screens | |
|
Business Unit
|
5 screens | ||
|
Category
Locked
Choose a category using a popup picker window. |
No screens | ||
|
Change reason
Choose the reason for the change request |
2 screens | ||
|
Change risk
|
3 screens | ||
|
Change type
|
3 screens | ||
|
Cloud Customer Name
|
4 screens | ||
|
Comment
|
Wiki Style Renderer | No screens | |
|
Components
|
19 screens | ||
|
Contributors
|
No screens | ||
|
Customer Impact Details
|
Default Text Renderer | 4 screens | |
|
Customer Impacted
|
4 screens | ||
|
Customer Notification Required
|
4 screens | ||
|
Description
|
Wiki Style Renderer | 23 screens | |
|
Design
Locked
Custom field that stores design information |
No screens | ||
|
Development
Locked
Includes development summary panel information used in JQL |
No screens | ||
|
Due date
|
4 screens | ||
|
Environment
For example operating system, software platform and/or hardware specifications (include as appropriate for the issue). |
Wiki Style Renderer | 4 screens | |
|
Epic Color
Locked
Epic Color field for Jira Software use only. |
Default Text Renderer | No screens | |
|
Epic Link
Locked
Choose an epic to assign this issue to. |
2 screens | ||
|
Epic Name
Locked
Provide a short name to identify this epic. |
Default Text Renderer | 1 screen | |
|
Epic Status
Locked
Epic Status field for Jira Software use only. |
No screens | ||
|
External Reference
Used to identify items derived from an external tool . Value is a concatenation of Tool ID and Item ID in the external tool. |
Default Text Renderer | 2 screens | |
|
Fix versions
|
8 screens | ||
|
Flagged
Locked
Allows to flag issues with impediments. |
No screens | ||
|
Goals
Locked
Link goals to issues |
No screens | ||
|
Impact
|
12 screens | ||
|
Implementation Plan
|
Default Text Renderer | 4 screens | |
|
Implementation plan
|
Default Text Renderer | 3 screens | |
|
Investigation reason
Reason for problem investigation |
3 screens | ||
|
Issue Type
|
19 screens | ||
|
Issue color
Locked
|
Default Text Renderer | No screens | |
|
Labels
|
22 screens | ||
|
Linked Issues
|
40 screens | ||
|
Location
Adding both UUID and Location fields to a project, will enable JIRA Mobile Connect for that project. |
No screens | ||
|
Locked forms
Locked
The number of locked forms on the issue |
No screens | ||
|
Log Work
Allows work to be logged whilst creating, editing or transitioning issues. |
Wiki Style Renderer | 1 screen | |
|
Major incident
Locked
Mark incident as major. |
3 screens | ||
|
Monitoring/Logging/Alerting Tools
|
Default Text Renderer | 3 screens | |
|
Notification Plan
|
Default Text Renderer | 4 screens | |
|
Open forms
Locked
The number of open forms on the issue |
No screens | ||
|
Organizations
Locked
Stores the organizations that are associated with a Service Desk customer portal requests. This custom field is created programmatically and required by Service Desk. |
12 screens | ||
|
Pair programming user
This field is used to indicate the user that the assignee has done pair programming with. |
1 screen | ||
|
Parent Link
Locked
|
No screens | ||
|
Pending reason
Specify the reason for moving the issue to the Pending status |
10 screens | ||
|
Planned end
Enter when the change is planned to end. |
3 screens | ||
|
Planned start
Enter when the change is planned to start. |
3 screens | ||
|
Post Change Validation / Testing Procedures
|
Default Text Renderer | 4 screens | |
|
Priority
|
21 screens | ||
|
Project overview key
Locked
Key of Atlas project connected via Atlas for Jira Cloud |
Default Text Renderer | No screens | |
|
Project overview status
Locked
Status of Atlas project connected via Atlas for Jira Cloud |
Default Text Renderer | No screens | |
|
Rank
Locked
Global rank field for Jira Software use only. |
No screens | ||
|
Reason for Change
|
4 screens | ||
|
Region
|
4 screens | ||
|
Release Note
|
Default Text Renderer | 4 screens | |
|
Reporter
|
20 screens | ||
|
Request Type
Locked
Holds information about which Service Desk was used to create a ticket. This custom field is created programmatically and must not be modified. |
Default Text Renderer | 11 screens | |
|
Request language
Locked
The language which a request was raised in. |
11 screens | ||
|
Request participants
Locked
Stores the users that are participants in service project customer portal requests. This custom field is created programmatically and required by service project. |
12 screens | ||
|
Resolution
|
11 screens | ||
|
Responders
Locked
Add responders to an incident. |
3 screens | ||
|
Restrict to
|
No screens | ||
|
Risk of Change
|
2 screens | ||
|
Rollback Plan
|
Default Text Renderer | 4 screens | |
|
Root cause
Describe the root cause for the problem |
Default Text Renderer | 2 screens | |
|
Satisfaction
Locked
Stores request feedback in service project requests. This custom field is created programmatically and required by service project. |
11 screens | ||
|
Satisfaction date
Locked
Stores request feedback date in service project requests. This custom field is created programmatically and required by service project. |
No screens | ||
|
Scheduled Finish
|
5 screens | ||
|
Scheduled Start
|
5 screens | ||
|
Scope of Change
|
4 screens | ||
|
Security Level
|
7 screens | ||
|
Sentiment
Locked
Sentiment is determined by content in the issue and latest comments from the customer. Content quality may vary |
No screens | ||
|
Service 1
|
2 screens | ||
|
Service 10
|
1 screen | ||
|
Service 11
|
2 screens | ||
|
Service 2
|
2 screens | ||
|
Service 3
|
2 screens | ||
|
Service 4
|
2 screens | ||
|
Service 5
|
2 screens | ||
|
Service 6
|
2 screens | ||
|
Service 7
|
2 screens | ||
|
Service 8
|
2 screens | ||
|
Service 9
|
1 screen | ||
|
Service Dependencies/Integration testing results
|
Default Text Renderer | 3 screens | |
|
Severity
|
3 screens | ||
|
Source
Captures the reporting source for this issue |
3 screens | ||
|
Sprint
Locked
Jira Software sprint field |
6 screens | ||
|
Start date
Locked
Allows the planned start date for a piece of work to be set. |
No screens | ||
|
Story Points
Measurement of complexity and/or size of a requirement. |
1 screen | ||
|
Story point estimate
Locked
Measurement of complexity and/or size of a requirement. |
2 screens | ||
|
Submit Date
|
1 screen | ||
|
Submitted forms
Locked
The number of submitted forms on the issue |
No screens | ||
|
Summary
|
Yes | 23 screens | |
|
Target end
Locked
The targeted end date. This custom field is created and required by Advanced Roadmaps for Jira. |
No screens | ||
|
Target start
Locked
The targeted start date. This custom field is created and required by Advanced Roadmaps for Jira. |
No screens | ||
|
Team
Locked
Associates a team to an issue. You can use this field to search and filter issues by team. |
No screens | ||
|
Template Approved
|
Default Text Renderer | 1 screen | |
|
Test plan
|
Default Text Renderer | 3 screens | |
|
Time to close after resolution
Locked
This custom field was created by Jira Service Management. |
No screens | ||
|
Time to first response
Locked
This custom field was created by Jira Service Management. |
No screens | ||
|
Time to resolution
Locked
This custom field was created by Jira Service Management. |
No screens | ||
|
Time to review normal change
Locked
This custom field was created by Jira Service Management. |
No screens | ||
|
Time tracking
An estimate of how much work remains until this issue will be resolved. |
14 screens | ||
|
Total forms
Locked
The total number of forms on the issue |
No screens | ||
|
Urgency
|
11 screens | ||
|
Verification Plan/Change resulted in expected outcome
|
Default Text Renderer | 3 screens | |
|
Vulnerability
Locked
Custom field that stores vulnerability information for JQL |
No screens | ||
|
Waiting for Reporter Counter
|
1 screen | ||
|
Work category
Locked
Jira system field that displays the category of work a specific issue belongs to. |
No screens | ||
|
Workaround
Describe the workaround for the problem |
Default Text Renderer | 2 screens | |
|
[CHART] Date of First Response
|
No screens | ||
|
[CHART] Time in Status
|
No screens | ||
|
uuid
Adding both UUID and Location fields to a project, will enable JIRA Mobile Connect for that project. |
No screens |