Why in the world does a workflow have to be uploaded to the Atlassian Marketplace to be imported??

Suzanne Raphael April 1, 2024

This is dumbfounding that I can't simply export a workflo/jwb file from one place and import it into another. What possible reason can there be for this??

2 answers

0 votes
Mark Higgins
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 30, 2024

Hi Suzanne,

I know its been  months since you posted your frustrations, and I've come across the same thing.

Seems straight forward, on the surface. but it obviously isn't underneath.

I'm guessing, much like customfields, that you call something in one instance, has a different number in the new instance, and I suspect its similar with workflows.

That why they look straight forward, the internal workings on how they work, require identifiers and those identifiers are unlikely to be the same across two instances

Atlassian has recently release a new feature from the Org level, called Data Management, and its 'designed' to allow you to copy JSM projects from one instance to the other. That includes workflows.

It's not 100%, as it renames some of the Status (but not all?), but it may be a way for you to bunny hop workflows from one instance to another.

Mark

 

0 votes
LynnG
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 1, 2024

Hi Suzanne,

Can you copy the workflow and rename it to reuse it?

It is not clear what your objective is.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events