Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


request type doesn't copy over when moving tickets from one Service Desk project to another

When we move tickets from one Service Desk project to another the end users have to select a request type, which is a pain. The values don't just copy over from project to project. Is there a way to fix this or is it an existing bug we're waiting to get fixed?

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 27, 2020

Hello @JJ

Thank you for reaching out.

Indeed, it is expected that you must select a new request type when moving an issue from one project to another. Please, allow me to provide you with more context about this:

Request types are basically used to allow your customers to see the issue in the customer portal and properly differentiate the type of request. They are mapped to issue types, however, each project has its own mapping.

Giving you a practical example:

  1. Let's suppose you have a request type A mapped to issue type A in project A
  2. In project B, this same request type (A) is mapped to Issue type B.
  3. If you move your issue from project A to B, it will not be possible to automatically copy the request types when moving the issue since there is no mapping with the current issue type.
  4. Going deeper on that, it is possible that a single issue type is mapped for multiple request types, so there is no way to know what new request type should be selected

We agree with you that the request type could be automatically set based on the issue type selected for the issue with a pre-determined request type, so we created the following feature request to improve the move client:

Update Request Type automatically when the issue is moved to a different project or different workflow 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

As a workaround, you can create an automation rule (Under project settings > Automation) to properly set the request type of new issues transitioned/moved, like the one below:

Screen Shot 2020-04-27 at 16.01.22.png

Let us know if you have any questions.

@Petter Gonçalves  I created a clone of a service management project with the same issue types and the same customer requests type names.

Why I can't retain the old request type value when moving to the other cloned project? (Cloud version)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events