-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Problem
Customers are looking to take advantage of the features that the ITSM service project template has to offer and would like to be able to move existing projects and configurations to the new template.
Suggested Solution
Allow to the ability to easily convert existing service projects to new ITSM Service Projects without having to go through recreating the project and new configurations.
Workaround
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-10171] Allow to the ability to easily convert existing service project to new ITSM Service Project
Not having the option is not fair to exist customers. We cannot make use of the ITSM features and migration is painful. We are being denied from Change management calendar, Incident Management, Opsgenie integration. An ETA would be really appreciated.
Having to recreate or reconfigure things such as a great number of automation rules and portal forms, etc, as well as bulk move 120,000+ service desk issue tickets (of which you can only bulk move 1000 at a time), from an existing classic service project is looking like an extremely strenuous and tedious process right now. Very much looking forward to a more automated transitioning process - in order to take advantage of Jira Service Management's new ITSM service project template - so we can resume business as usual with a service project that has all of our historical service tickets while making use of all the new features JSM has on offer as part of the new ITSM service project template/type.
Right now the road ahead to plough through and try do this all manually so that we can get to that endpoint - well, it is looking really rough. The sooner an automated solution is implemented for this the better! 
Can we have an indication on the eta is this something that might be considered in 2022 or customer are to expect to raise a business case for an extra resource to do the proposed "workaround"?