This message was deleted.
# general
s
This message was deleted.
j
Hi, There is a feature already existing in Jira to create a Board using an existing one. We use it all the time to keep Jira clean.
It is for “Company managed” Project
s
Just to add to this, if people only answer to a single board, you might not have a problem. Forcing people to share boards is a quick way to remove their ability to define and improve their own process. If people have work on more than on board, that's definitely a situation where consolidation may be needed.
d
Oh yeah - totally agree. I didn’t mean to suggest that teams don’t have their own boards. Just perhaps some higher level templates
Also, I’m not fully sold on the problem statement. For me teams should be totally autonomous in how they name things etc… but seeing as big wigs want some analysis done, thought it best to see if others have faced the same issue
j
Your are right. We face the same. We defined some rules internally and we tried to defined Schemes for Workflow, Issue type, Screens and Permissions. The idea is to deploy project using those scheme instead of default ones as Jira recreate everything for each. new projects. Reusing an existing project avoid Jira to create everything. It helps admins in maintenance.
d
If I may ask - did you just setup one, empty project the way you wanted and then use the setting in the above screenshot when creating new boards (so that they inherit from that board)
Or.. maybe something more complex e.g. GitOps based
j
Yes we created some project as exemple and then we reuse them when we want to create similar ones. Please note that new project are empty of issues and empty of members. Project just inherit from Issue type, permissions, workflow, ... Using API you can also automate deployment.