Hi @Zach Detwiler and welcome to the Community!
What you are asking about is what essentially any organisation that uses Jira as a corporate application should be doing: have some governance in place when necessary, manage the configuration so it scales and creates some sort of familiarity across projects, teams and users.
I would not recommend to go for one single screen to cover literally all projects across your instance. Suppose you have software, ops, HR, marketing and legal teams all working in Jira, you can imagine that giving them all the same screen would lead to quite nonsensical situations where certain people or teams will not recognise many of the information on that screen.
It does make (a lot of) sense to build screens for similar types of work. If you use stories, make sure you have everything on your screens that is needed to make them a story. If you manage a sales process with opportunities, make sure you can identify e.g. the budget and customer, ... information.
Use issue types and screens, screen schemes and issue type screen schemes in combination with company managed projects to create shared configurations across projects that are meant to manage similar types of work.
It wouldn't make much sense to just share "a standard screen" from another company, since making Jira user friendly and adopted by your users requires you - as an administrator - to set it up in such a way that your company users recognise their work in it. That means: setting up fields named in alignment with the terminology you use for your business.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.