Maintain 'Request Type' value when moving issue

[Ben Rao]

As part of an ongoing tooling upgrade, we have built a brand new JSM project without our JIRA instance with new workflows, fields, etc

We are now looking at migrating items from our previous JSM project to the new project. When moving the issues, we have mapped statuses, fields, etc, but we are having problems with the request type field.

We aim to keep this value the same as the previous project, but by default, this is cleared when moving, meaning the issue in question disappears from the customer portal.

Is there any way to maintain/map this value that does not require each request type's issues to be moved individually? The types exist in both projects, and the names match.

[Florian Bonniec]

HI @Ben Rao 

There is not much you can do I think as Request type is related to the project. You could create an automation that set the new Request Type based on the the issue type.

https://confluence.atlassian.com/jirakb/automatically-set-customer-request-type-when-issue-is-moved-or-created-via-jira-1026039858.html

Regards

[Raphael Lopes]

Hello @Ben Rao 

Do you know phyton, if so, I have two scripts that I run, one to extract the issues that have been migrated and that are without the Request Type filled in and another script that updates these issues with the old request types. They just need to exist in the new project.

[Ben Rao]

Hi Raphael,

I have some experience, but we have a host of developers who have experience. Would you be happy to share those scripts with me?

Thanks

Ben