How can I import/export a workflow to/from a team-managed project?

[Rob Holmes]

I wish to create multiple team-managed projects all with the same workflow.  How do I copy a workflow from one project to another? Ideally this would be via the GUI but if I need to use an API then that's OK.

Googling suggests this isn't possible and I need site admin status and company-managed projects to achieve this.  However, this strikes me as pretty basic functionality so I'm hoping that this is not correct. Can anyone confirm?

[Terri Sanfilippo]

This same issue just came up for us too. Apparently it's not possible but someone has submitted it as an enhancement = https://jira.atlassian.com/browse/JSWCLOUD-21700?error=login_required&error_description=Login+required&state=e5ba7d66-f458-4a8b-973e-6c2fcae57088 so you can vote and watch it.

[Nic Brough -Adaptavist-]

Team-managed projects do not really have workflows as distinct objects, they have a set of rules defined by the team that owns it.  

There's no export/import or sharing of these rules because the project belongs to a single team and the whole point of a team managed project is that it dedicated for that team.  If you want to enforce the same process across several teams, use a company-managed project.

[Rob Holmes]

Well my team will have multiple similar projects and we'd like to apply those rules to each project in the same way.  If we have to do this manually each time then it is painful and prone to slight deviations. We have got company-managed projects but as our company is large it is cumbersome to try to manage a set of workflows to keep all teams happy. It also means that for me to set up a new company-managed project requires raising a ticket with our IT dept, thereby slowing the process. 

Thank you for the confirmation that there is no way to achieve this for a team-managed project.  I disagree with the design thinking behind it, but appreciate you taking the time to respond. 

[Daniel Sputa]

i second this. -- the point of sharing workflow for team projects is not to enforce the same workflow but rather to use a template with the workflow to apply to the team projects. I have recruiting projects for each role and I don't want HR forks being burdened with the company/classic Jira project.. rather I want to have team projects for the recruiters to move the candidates through established steps that are common for all their projects. 

[Nic Brough -Adaptavist-]

Yep, I understand the case of "using it as a copy", but the point here is there's no actual workflow in a team-managed project, it's a looser pile of rules, and there's no export/import, or even copy.

[René R]

100% agree with Rob.

[R_ Sage]

Even if you don't care about sharing, I support a team and want to archive the workflow so that it can be restored if an administrator breaks it. 

How do I do archive/export or restore/import?  It is archive/backup and restore features that many people use on various tools to share data.

[Nic Brough -Adaptavist-]

It's the same answer - TMPs don't have anything you can export, backup, copy, or archive.