Why can’t you add fields to the default template - not working!

[Desiree Olivito]

I have tried everything and have heard this used to work. We would like to add two fields to the default template so every time we create a new project the two fields are added. I don’t want to have to associate the new fields with the new projects screens every time I create new projects. It should happen automatically. 

In reviewing past topics it seems someone suggested a workaround to create a default project and when creating new projects share the properties of this new projects. And that actually works but then the new project has no boards or backlog. So I have traded one issue for another. 

It seems this should be basic Jira functionality to be able to add a field to a default template and have any projects currently using the template to be updated, and any new projects created would have the new field as well. Help!

[Hernan Halabi - Elite IT Consulting Group]

Hello @Desiree Olivito you only have the two options you mention and I would suggest you use the second one using a project as template and create boards for each project. Creating boards doesn't require admin permissions so the project owner could config his own board and if you later need to add a third field you will have to do it only once and the change will impact in all the other projects since they share the same configuration. If you do it the other way you would have to add the field into each project configuration

[Desiree Olivito]

Thanks for the feedback @Hernan Halabi - Elite IT Consulting Group 

It makes sense to use the project template as you mentioned.  In testing the impact of proceeding with this approach, I have found additional burden will be placed on the Jira admins.

By using the shared default schemes/workflow in the default project, the project admins will not be able to add columns to their boards as this modifies the Simplified Workflow SHARED by all the projects using the default project. They need to contact a Jira Admin to do so.

I feel this is an inherent flaw in Jira to jump through hoops to add fields to the default template.  This should be a simple straigthforward requirement. I don't know if this is a bug or intentional but the need to add fields to the default template should be straightforward and apply to all the projects that use the template - including newly created projects.

[Hernan Halabi - Elite IT Consulting Group]

I wouldn't recommend allowing simplified workflow since the results of that is that your instance ends being confusing and far away from standard because each one named theirs status as they pleased. You end having a done, closed, finished, complete ready, etc as an end status so reports are more complex and in the end you will need to standardize which leads to a lot more work than admins creating the workflows for the users. 

This is the good and bad of Jira flexibility, you can do the same in more than one way. Only experience will help you identify which one works well in the long term