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

Is it possible to clone request types?

Juan Ignacio Tel

Hi there,

We are starting with JSM and would like to create several request types with small differences on their configuration between them, so it would definitely be useful if we could clone them.

Is there any way to achieve it without having to re-create them from scratch?

Any help will be appreciated.

Thanks in advance.

Accepted answers

Connor_lld39i

Yes it's possible, go to Project settings --> Request types --> click options button beside the request type --> click Duplicate --> follow the remaining prompts. That will create a new request type with identical settings to the original.

All comments

Connor_lld39i

Juan Ignacio Tel

Thanks for your indication Connor.

Maybe I'm totally missing it, and of course we're newbies, but I think I already tried that (as most logical way to find the option).

When I click on the ellipsis button, the only available option is "Delete request type".

I'm admin so and I can fully edit or delete the request type.

I saw this article Duplicate request type available in Jira Service M... - Atlassian Community but, in the same way as one person comments that is not seeing the duplicate option, neither I am.

P.D. Sorry, I forgot to mention that we're using JSM on Cloud, using IT Service Management (Essentials) template, team-managed project, just in case that's relevant.

Connor_lld39i

Yeah it looks like this is only for company-managed projects. The user commenting on the article you linked states:

I cannot see the list as in the screenshot here, When I open the Request Types section. screen goes directly on the first one.

I've tested on a team-managed project (TMP) and I see the same behavior. There are no request type categories in a TMP, so you're taken straight into the configuration of the first request type in your list. Just another of the many reasons to not use TMPs.

Juan Ignacio Tel

Thanks for your testing Connor. That clears up the matter.

I fear that we don't have too many resources on our org, and TMPs have allowed us to start our JSM journey in a more friendly way.

You've kind of frightened me: I'm pretty sure that TMPs are not the pro-way of dealing with JSM, but reading your answer it looks like there are a lot of reasons to be away from them.

Any specific advice knowing that we're around 100 users ("clients") and no more than 4 agents?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

request-type

jira-service-management-cloud

jira-service-management