nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JSM Portal - Selection Criteria for Requests

Joni Johnson

For the JSM Portal, you have Requests in the upper right. What is the selection criteria that drives what is displayed on that? For items to be considered close, are there specific resolution fields such as resolution, resolutiondate that must be filled in for items that may have a closed status to drop from the view when only wanting to view Open Items.

Accepted answers

Kate Pawlak _Appsvio_

Hi @Joni Johnson ,

You have to fill in a Resolution field. This Open/Closed filter is based on this field. If it's Unresolved, the request is in the Open category.

Kate

All comments

Dan Breyen

From what I can tell, it's going off of Status. So a 'Closed Request' needs to be 'Resolved', 'Canceled' or 'Closed' status.

Joni Johnson

Thank you. That is not what I am seeing. We customized our workflow to allow JSM tickets to go to Closed without going to Resolved. Items that are closed that did not go through the resolved state are still showing.

Kate Pawlak _Appsvio_

Hi @Joni Johnson ,

You have to fill in a Resolution field. This Open/Closed filter is based on this field. If it's Unresolved, the request is in the Open category.

Kate

Joni Johnson

Thank you. That is what I thought and wanted to confirm.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management