We have discovered that we have 114 projects sharing one workflow. This workflow has issues from many different projects.
One of the project leads reported his project is not working correctly. We did not notice the shared workflows till now. Should every project have it's own workflow? Does this setup create problems?
There is not inherient issue w/ sharing workflows across projects and in fact can make things much easier to maintain. With that said, it can be rather limiting since many projects/teams don't work the exact same way as other teams. I would not be surprised that trying to maintain a single workflow across 114 projects would eventually lead to issues or the need to diverge. My advice would be to react to the changes/needs of projects as their WF requirements change.
You mentioned that one project wasn't working correctly. What exactly isn't working? Can it be addressed by simply making a copy of the current WF, editing to meet the needs and the associate to the issuetypes in that project?
p.s. you may wish to remove your email as this is a public forum but that is your call of course.
Thank you for the information. I have sent an email with the issues with the project. The user has issues that are closed but still show up on his activity list.
Is there a recommended way to make a copy of the one workflow that is in our Production system. If a project admin wants a new workflow then we have it for them.
What is the recommended way to create a new blank workflow for project admins.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events