Do you use the Workflow importer workaround? Let us know

[#1]

Hey all,

I'm Rhys, a PM on Jira Administration.

You may be aware that there a Cloud->Cloud workflow import workaround offered today. It’s clunky and relies on customers creating a Vendor account to process the import.

This workaround is far from an ideal experience and there are challenges with it that will prevent us from supporting long-term.

We therefore intend to deprecate this workaround. We are reaching out to the community to understand if you will be impacted and appetite for a native Cloud->Cloud workflow import solution.

If this deprecation affects you it would be valuable for us to better understand your usage/use case and if its future deprecation would impact your operations.
So please let us know!

You can also vote on this ticket for a native solution: https://jira.atlassian.com/browse/JRACLOUD-69079

Kind regard,

[Kiam Venter]

Thank you for letting the community know, luckily, it does not affect the project I am currently on.

[Rick Westbrock]

During our initial implementation of JSM Cloud I wrote a script that reads the JSON file of a workflow exported from our sandbox to update any environment-specific values such as field IDs or screen IDs then uses the API to import it into the target.

Today we sometimes have users who build or modify a workflow in our sandbox then need to deploy it to production so I have them export the workflow and I run it through my script but that's not an ideal solution and I never had time to enhance the script to account for field IDs inside of validators and that sort of thing.

Providing users who do not have admin privileges the ability to import into production a workflow which they built in sandbox would be helpful for us although to be fair that only comes up maybe one or two times per year at most.