Request type removed when moving issue to another project

[Deleted user]

Afternoon, quick question.  We have 3 separate ServiceDesk projects for 3 different teams that share issue type schemes, custom fields, etc.  The issue is that when we move from one project to another it keeps the type but clears the request type.  Clearing that kills our notifications and doesn't allow the reporter to see the issue in the portal.  What is wrong with my configuration that would cause that?

Thanks
Jason 

[Susan Hauth _Jira Queen_]

On cloud, I don't think there is.  THere might be a way to create and link a new issue.  Then you could use automation to keep the front service desk request updated, while the VSTS issues are worked on.

Just an idea

[Susan Hauth _Jira Queen_]

Hi Jason,

Nothing wrong with your configuration, it's just that request types are not global items and therefore cannot be migrated from one project to another. 

I'm surprised there isn't a prompt to change the request type as part of the move step. 

Wondering why you need these in different service desk projects if you're passing them back and forth?

Hope that helps

Susan

[Deleted user]

Hi Susan, we have an other project that syncs with VSTS work items.  We made it a separate project so it would only sync items in that project.  Basically our primary ServiceDesk project handles all incoming requests.  Then if they need to be escalated to VSTS work items we move them into a second project.  So basically I we will just have to set these manually.  I don't think there is an automation trigger for in an item is moved to a project?

Jason