+1

Please, do it

+1,

On Cloud please implement this, Its necessary.

Thanks!

+1 need this

This should be out of box thing to change the configuration from Admin perspective

Sorry Atlassian its becoming too cumbersome to manage your products, we are exploring new tool sets for these reasons

+1 NTH

@jehan,

The biggest thing here is many hours are spent making Service Desk Request types. End users may select one Issuetype to map it to but then change there mind.

We have Hundreds of request type in our Jira instance. Sometimes having re-create a whole request type just to change the issuetype is time consuming and a huge pain especially if a team has decided to make several changes to their Service Desk. 

My currently example is a team created their Service Desk Request and forgot to change their Issuetype, not they have to recreate over 20 request types. Which means re-mapping the fields and all the text was entered. 

One solution that I can think of is just allow a Copy Request type option that keep all the Request type text and field renaming but allow for customization and changing Issuetype. 

Also I can't access your survey. 

@Jehan,

docs.google is blocked and not agood vehicle. I just typed a longer response, but it didn't show after I clicked save.

Hi everyone,

I'm a product manager at Jira Service Management and I'm looking to understand the need here so we have a better understanding of how this could be solved.

If you are able, we'd love for you to complete this survey so we can get your more detailed feedback and collate it.

Please click here to complete the survey.

Best regards,

Jehan

Yeah, same here.
Also not just dete and re-add request types, but

• re-map,
• rename,
• reorder or
• hide and give value

to dozens of custom fields behind a request type field mapping or workflow mapping.
:/

So irritating that you can't even change the default ones that you can't delete, so unable to delete and re-add 

Instead of spend effort to implement a basic function to increase customer satisfaction, they have deceived to change product name  

This should just be a basic functionality of JSD. We now have to manually move 30 requests per project (15 projects) which makes no sense. Please implement this fast, as it makes it very uninspiring to work with SDP's.

7 years later and this is still a missing feature. This should be a basic Edit task. Instead, I have to go through all the work to recreate just to change the issue type?!

thumbs up, that would be very helpful!

So frustrating! Request types created with wrong issuetype have to be recreated!! This can takes hours if you have a lot of request types!

This seems like basic functionality... Guess I am deleting and recreating a bunch of request types.

hi, i would like to configure the default "Emailed Request" request type but couldn't because it prompts

"We couldn't load your request type

You can't edit the request type because the issue type it's based on was removed. To restore the request type, add back its associated issue type in this project's issue type scheme."

how do i configure the mapping of request type-issue type?

Hi,

Is this request being worked upon?

I don't see this assigned to anyone!

Thanks,

Krishan

Please implement this!

Need this feature ASAP 

Thank you,

Ravi

I am a new administator and was very excited to have created all my Request types until I realised some had been associated with the wrong Issue type.  Would be great to see this functionality added in the future so we don't have to recreate from scratch.

@Katherine Stevens

If you're cloud, go to settings, and on the left-hand menu there is an "Email Requests" option. 

How do you change the Emailed Request - Request type to a different Issue Type.  Right now the associated issue type is service request.

At the very least, you should be able to change the Issue Type of a Request Type that is NOT currently used/mapped to any issues.

I need to change issue type and this feature is very important to me!

+1 for this, very strange it is not baseline functionality.  Quite tedious having to delete and restart fresh if you choose the wrong issuetype/have updated customer need....

++ what an immature product.

I was facing the same issue today and I manage to change it with a SQL statement:

update "AO_54307E_VIEWPORTFORM" set "ISSUE_TYPE_ID" = <new_issuetype_id> where "ISSUE_TYPE_ID" in (<old_issue_type_id);

Ofcourse you should first check, if you probably need to check which portal needs to be changed. And therefore you can just use this simple select statement and check the IDs:

select * from "AO_54307E_VIEWPORTFORM";

note that you have to add the issue type already to your issue type scheme.

I mean sure... this is quite a hacky solution, however it does the trick without doing all the manual work

Mike DiGiantomasso makes a great suggestion above.  If an Issue Type change on existing Request Types isn't feasible, at the very least a clone option would be extremely helpful. 

I just ran into this, and now I have a lot of work to do to recreate requests. Ugh!

I would really appreciate it if this could get picked up soon! It's not possible to scale out and rearrange our request types and workflows now without deletion and recreation .. which will take hours to do. 

Would love to have this function come into the software... need to recreate the whole portal now... 

if there was a way to copy request types and change it then, that would help too.  i could delele the old one and rename   deleting request types is not feasible as there are many customizations

With all of the customization that goes in at the Request Type level, this is a major issue. We were migrating our entire IT department to Service Desk from ServiceNOW. We had everything laid out including about 25 some groups with about 5-10 custom request types per group when we discovered we could not change issue type...start over? Remap all field customization's and statuses? This really needs to be a fix...like, ASAP!

This ticket is in reference to the Service Desk Administration area, where the Request Type forms are defined.

Agents can use "Move" to change the Request Type and/or IssueType. Can clients/users be coached to request the Agent to change as needed?

This is a major problem, and as usual we don't know if or when it will be addressed.

Good luck scaling your Service desk! Wanna switch issue types? Too bad! Delete it all and start the heck over.

This feature would be very important to me. Otherwise, I have to rebuild the whole 12 request types. Each of  them with many fields and functions. This takes hours...

To copy a request type ist also not possible!

I was surprised this isn't default functionality. I entered a dozen or so Request Types and realized they all had the wrong issue type on them. I had to delete them all and start over which is a giant waste of time.

Agreed. But not knowing the original requirements of the system I would have no idea if this was a defined feature at the time. If it was than yes they should be treating this as a "Break-Fix" not an enhancement. Is this ticket not assigned to anyone?

I would say that it is close to a bug that you cannot change the issue type on a request type... you can edit/change the other fields

Hello, Just wondering if this feature request is getting any traction? Seems like obvious benefit.

Tanguy, it means the ability to change the issue type of a request type on the customer portal without having to delete it.

imane.assoud@ovyka.com does it mean having request type applying for not only one Issue Type but more likely a couple of issue Types ?