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; } } }

Create request type/work type does not work

Antonia

I have created a new request type in my sandbox so that I can test it there first. Now I wanted to create a request type in my live environment and somehow it doesn't work there. I can only create a type within a request type, but I want to have a completely new work type so that I can click on it when I want to create a ticket.

Screenshot 2025-07-23 113137.png

Accepted answers

Trudy P Claspill

Hello @Antonia

One thing I note about the images you initially presented is that while they are both from Service Management projects, the one on the left is a Company Managed Service Management project and the one on the right is a Team Managed Service Management project.

Those two project types handle Request/Work Item type creation differently.

In a Company Managed JSM project Work Items and Request Types are two separate but optionally connected entities. Request Types are what a customer can select on the customer portal. A Request Type has to be linked to a Work Item Type, and selecting a Request Type in the portal results in creation of a Work item of the associated Work Item type. A Work Item Type is what an Agent can select when they create an issue using the Create button within Jira. In Company Managed JSM projects it is possible for an Agent to create a Work Item that is not linked to a Request Type.

In a Team Managed JSM project it is not possible to create a Work Item without it being associated to a Request Type. So in TM JSM projects you have the option only to create Request Types, which are synonymous with Work Items.

All comments

Evgenii

Hi, @Antonia

Isn't it the same? You can create request type from this button.

Antonia

Hi @Evgenii

thank you for your help.

I have created a request type in the sandbox and if I then go to Create work item at the top, I can select this type as the work type. Unfortunately, I can't do that in the live environment. There it simply appears as a request type and not as a work type.

Screenshot 2025-07-23 115121.png

Evgenii

In a few words, here’s how request types work in a Jira Service Management (JSM) project:

First, create a work (issue) type .
Assign a workflow to this issue type.
Add the issue type to the issue type scheme of the relevant JSM project.
Then, create a request type and link it to the corresponding issue type.
Add request type to required category on portal

Once linked, the request type will appear in the customer portal and will create issues of the specified type when submitted.

Antonia

I searched for "create work (issue) type" but I couldn't find it. Do you know where I can create one?

Trudy P Claspill

Hello @Antonia

Those two project types handle Request/Work Item type creation differently.

Antonia

Hi @Trudy P Claspill

Okay, thanks. That explains a lot.

Trudy P Claspill

So, in a Company Managed Service project you find the work items listed here, in a Work Item Type Scheme that is associated to the project. You can modify this scheme to add more Work item types to it that have already been created by a Jira Admin. (The creation of new Work Item Types by a Jira Admin is done separately through a different screen.)

Screenshot 2025-07-24 at 7.38.20 AM.png

And then also in the project you can create Request Types (in this template they are in groups) and associate the Request Type to the Work Item Type that will be created as a result. And in these projects the Request Type can have a different name than the associated Work Item Type.

Screenshot 2025-07-24 at 7.36.05 AM.png

With Company Managed Service projects, the Project Admin can create new Request Types, but not change the Work Item Types available. Only Jira Admins can change the Work item types that are available.

In a Team Managed Service project there is no separation in the creation of Request Types vs. Work Item Types. Instead in Project Settings there is one entity (Request Type) with two sections grouping the fields seen on the view from the Customer Portal (red square) and then the additional fields seen by agents in the Jira UI (blue square).

Screenshot 2025-07-24 at 7.45.00 AM.png

In a Team Managed project the Project Admin has full access to add Request Types (in Service projects) and Work item types (in non-Service projects) so I guess Atlassian decided there was no need to separate those entities in the Team Managed project.

In your Sandbox you used a Team Managed project. If you want to have the same set up options in your live environment you need to have a Team Managed project created there also. Currently, with have two different types of projects you are going to have different experiences with what can be modified and with other functionality.

Antonia

Hi @Trudy P Claspill

thank you very much for the explaination. So I was searching the whole time for the categories and these can't create yourself. That was my problem, so thank you!

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