can you import a workflow from an XML file in Jira Cloud?

[catherine.lee]

I am a global administrator for our Atlassian suite and I followed the path described at the beginning of this article (Administration settings cog > Issues > Workflows) but I don't see the "Import from XML" button. There is only the option to Import from the Marketplace.
My company uses Jira Cloud; do the instructions on this page not apply to Cloud? Is the "Import from XML" function available for Cloud?

[Deleted user · Accepted solution]

Yes, it is possible. However,  it would require you to upload the workflow (.jwb format only) as a public workflow in the Atlassian Marketplace first before you can import that into your Jira Cloud instance.

Kindly refer to the following documentation for the steps on how to import a workflow in Jira Cloud.

https://developer.atlassian.com/platform/marketplace/knowledge-base/how-do-i-import-a-workflow-into-a-jira-cloud-instance/

Please be noted that the workflow that created Jira Server that contains third-party workflow post functions, conditions or validators might not be working in Jira Cloud.

Thank you.

[Eric Brahmann]

Hi @[deleted] ,

I am just wondering, why you need to store those workflows in the Marketplace.
I would like to locally back up my workflows, seems to be much easier.
Is there already an Issue in the Jira Cloud Project open, so i can comment on that?


Eric

[Wojtek Tomalik]

Uploading a workflow to the marketplace just for the sake of sharing is a HUGE pain. You need published customer terms and everything. This is completely ridiculous that you can't just import an exported jwb file to another cloud account, or share between cloud accounts that your account has access to...

[Ramin Shanehsaz]

Hello everyone,

we understand the frustration about the limited capabilities of exporting and importing workflows in Jira Cloud. We faced similar problems when configuring numerous workflows in a sandbox and manually replicating them in our production Jira.

To address this, we’ve developed Workflow Wizard, a new app that lets you effortlessly export workflows from any Jira Cloud instance and import them into the same or another instance, including all workflow data such as app functions and more. Also, you can create backups of your workflows and save them locally.

No more manual recreation or risk of errors—Workflow Wizard simplifies the process, saving you time and effort.

Check it out on the Marketplace:  🪄 https://marketplace.atlassian.com/apps/1234751/workflow-wizard

and refer to the documentation for more details.

We hope this helps make your workflow management easier!

Best regards,
Ramin
Dev Wizard
Computerra

[William Wilson]

Yep... Because that's what we need. Instead of Atlassian doing their JOBS... We need third parties to create MARKETPLACE ADD-ONS, so that the product (that some of us pay 6 figures for, annually), can spend MORE money... to do something the core product should do!

ALL SO THAT ATLASSIAN CAN DIP INTO THOSE SWEET MARKETPLACE BUCKS!

Don't get me wrong. I'm not trying to be critical of your work. I'm grateful that someone was willing to put in the effort and do the work. But you were put in this position... Because ATLASSIAN is NEGLECTING CUSTOMERS ON CORE ISSUES.

As a consumer, I'm *TIRED* of being nickel and dimed to death. Or having the product I purchased in good faith, increase in cost, while features I PAID FOR... get sunset or moved to the Marketplace, so that I can pay more for them.

Thank you for your hard work. But................... At our licensing level, that's another $5k/year to do something we shouldn't have to pay for in the first place!

And what's worse is, having this option out there not only de-incentivizes them because of lost revenue for them... but, how are you going to feel if they DO decide to finish rolling something like this out, and kills your revenue stream on something you worked to build?

It's dirty pool the way they are playing at this.

[Ramin Shanehsaz]

Hi William,

thank you for your feedback and acknowledging the effort put into creating these add-ons. I understand your frustration about paying extra for features that could be part of the core product. Your points are indeed valid.

In response, I was able to have the pricing of our app adjusted, since we are new at the marketplace and hope we can provide value and address the gaps in the core product. It can take some time until the pricing is updated in the marketplace.

Best,
Ramin

[Sanwar Mal]

Seriously!,  Why you give option to export locally if import is possible only via marketplace.

Product managers at Atlassian must be having just fun at work. It's a simple functionality been made complicated.

[Andrey Ivanov]

Actually, this is not even possible to publish exported workflow in Marketplace as it contains, at least, "Internal" company data.

Ridiculous... Is it true that we can't simply export and import our internal workflow between our Server and Cloud instances without letting anyone see it?

[Clemens Loipersberger]

Hi,

I just came accross the same issue.

I need to ex- and import in an easy way and not with additional steps (marketplace)

Is there any other solution or workaround?

[Mark Higgins]

Hi Clemens,

There is a new Feature at the Org level, under Security called Data Manaegment, that allows you to copy a project from one instance to another.

We tried it, to see if the workflows came across, and they did, sort of. SOme of the status where renames, but not all of them, and not the ones we expected.

If you have ORg access to the two sites, you could try to bunny hop a work flow from Project A on one site, to Project B on the other site, and then move the workflow into Project C, where I suspect you want it.

Let me know houw you go.

Cheers

Mark

[William Wilson]

@Mark Higgins Yes. There is an option to do this. But you failed to mention that if you do, and any of the fields you've used already exist in the destination, they will ALL BE DUPLICATED. EVERY. SINGLE. TIME. YOU. DO. THIS.

[Mark Higgins]

Hi @William Wilson 

I failed to mention it, because I wasn't aware of it

I'll refrain from assisting you in the future.

Mark

[Sami Ahmed Shaik]

I'm curious about the architect at Atlassian responsible for designing the cloud workflow model. 

This makes our life hell for the post-migration activities, and Atlassian expect us to migrate to the cloud with broken cloud architecture.

[William Wilson]

@Mark Higgins I apologize for the perceived tone. I didn't mean to sound hostile at you, and I certainly didn't mean to imply your help was bad or undesired. 

My use of caps is simply my frustration with Atlassian and their cadence of 1/2 complete or bug-ridden roll-outs. Among a laundry list of other issues driven by their refusal to communicate effectively with their customers. 

But I *AM* grateful for people out here helping. Please accept my apology for the confusing tone?

[Mark Higgins]

Hi @William Wilson 

Thanks for your reply

We are all good and I understand the frustration when Atlassian roll  out something as a 'Beta', and then you find out, its lame, and makes a mess.

I should have understood your response and not take it personally.

Have a great weekend

Regards

Mark

[Adnan ÖNCEVARLIK _IDEA Bilişim_]

You need to travel around the world a few times and also apply to the Market Place with a residence permit, visa approval and health report from the government. If you get permission from there, then you need to keep your XML file and convert it into an application (.jar, .jwb etc.). I don't understand how such a simple export process can be turned into such a long and laborious process. It's ridiculous, unnecessary, stupid. If XML can't be imported, why are you exporting? A solution should be found for this as soon as possible.