Jira Service Desk allows you to customize the fields where information is collected from your customers in the help center as well as customizing the fields of information used by your agents. Jira Service Desk does this through issue type fields and screens. Fields help agents investigate, assess, and categorize the incident for reporting or querying.
By default, the following fields are in your agent’s view of an incident. If you require additional fields, you can also add custom fields. Find out more about fields in Jira.
A short description of the request.
The person who submitted the request.
Segments of your IT infrastructure that relate to the request. For example, Billing services or VPN server. These are used for labeling, categorization, and reporting.
Files or images added to the request.
A long, detailed description of the request.
A list of other requests that affect or are effected by the request. If your business uses other Atlassian products, this list may include linked development issues.
The team member assigned to work on the request.
The importance of the request's resolution, usually in regards to your business needs and goals. Sometimes, priority is calculated by impact and urgency.
A list of additional custom labels used for categorizing or querying records.
A list of extra customers who take part in the request, for example, people from other teams or vendors.
A list of people responsible for approving the request, usually business, financial or technical contacts.
A list of customer groups interested in the request's resolution. Learn more about configuring a project.
The effect of the incident, usually in regards to service level agreements (SLAs).
The time available before the business feels the incident's impact.
A short description or code that indicates why the incident is not progressing.
A category of IT asset or system that the request effects.
A category of action or function required to fulfill the request.
The asset or system where the incident originated.
Was this helpful?