-
Suggestion
-
Resolution: Unresolved
-
697
-
44
-
Right now we need to setup workflow for each project and it's very time-consuming. Ability to copy Workflow to new Team Managed projects will be much useful
- duplicates
-
- Closed
- is incorporated by
-
- Future Consideration
- is related to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
[JRACLOUD-83240] Ability to copy Workflow to new Team Managed projects
would be helpful - was not aware of this limitation before our product team spun up several teams boards
Another upvote. Its a significantly painful limitation to team managed projects. It needs a solution.
This is blocking my ability to migrate from a team managed project to a company managed project (which I only have to do since team-managed project workflows cannot modify any Person fields)
upvote! it's painful to recreate similar workflow for the different projects that are being regularly added for our team
Highly recommended features! Especially we have complex workflow. Hopefully this comes true.
I think Jira is worried about programmers not having enough to do, and hence forces us to recreate literally every single thing by hand every single time.
While I appreciate the concern for my employment, I would really prefer to be able to create a Jira project and then re-use it over and over, instead of clicking and typing every single setting and form by hand every single time.
Related ask, as Jira's workflow graphing can very messy with overlapping lines etc. - would be helpful to be able to export the states and transitions for presentation to team members
This is a a basic feature. It should not take this long to get the made available.
Very disappointed in Cloud Jira
Another Vote in the affirmative. We could definitely use this feature. 
This functionality would be very useful in the case when the team decides to switch to team-managed project.
Bump.
This would make a huge difference.
In our small team, the simplicity of set-up for Team managed compared to Company managed projects is a massive benefit. But we do have multiple projects and plan for many more, so the lack of this feature reduces that benefit a huge amount.
We invest alot into creating a great process and workflow. Implementing that is painful because of the busy work to recreate it in every new project. Please Atlassian, make it so that we can easily copy workflows and issue types between projects. Jira is the best and easiest at so many powerful things that we need to organize software work; be the best and easiest at organizing software process, too!
I vote to add this enhancement because the same team may be working on multiple projects internally which need to be tracked by their own scrum board with the same swim lanes. This seems like a trivial export / import function.
Hi Atlassian, I agree with the comments, creating the workflows every time from scratch is very time consuming. This would be very useful to have for team managed projects.
Please include my vote. Currently, the Integration Team is establishing a standard template Jira project and is planning to clone it to a new project. As part of this I need to copy the workflow from the template Jira project to the new Jira project.
35 votes. I predict this will have a couple of thousand votes by the end of 2023.
Alternately, there could be a shared workflow for teams, if all projects need much the same workflow. However, being able to copy workflows would help immensely.
This enhancement would solve the difficulty in setting up and maintaining workflows if the teams have any substantial number of projects. This would eliminate a major barrier to the use of workflows. Thus, this would encourage use of workflows.
This would be a much-desired functionality of Jira. VERY HIGH PRIORITY!
I just spent an hour trying to figure out why I wasn't able to copy or duplicate workflows between projects (team managed).
Outside of the current limitation to do so against team managed projects (i.e, this filed issue), I'd like to propose adding some sort of noticeable disclaimer or help documentation within workflow screens associated with team managed projects that articulates this unique caveat.
Extra credit: In whatever form the caveat notice were to take on, we should add a link to this particular ticket in order to generate awareness and support for the feature. I think it's fair to assume that very few team managed project administrators are taking the time to track down why this feature doesn't exist.