The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
As a new administrator to Jira i am curious to hear how all you other administrators handle project creation for you companies/customers.
- Do you use shared configurations? if not, what is your process for project creation?
- When do you use shared configurations?
- Have you stumbled upon issues with shared configurations (overlapping schemes etc)?
Thank you in advance for sharing your insights!
//Gustav
Hi John! Cheers!
What you are telling me makes total sense! It is as i expected. The standard scrum and kanban template projects always auto-generate a bunch of schemes, which to me seem to clutter up the instance quite fast.
Doesnt seem too much of a drawback to copy and tweak schemes when needed!
Thanks for sharing your experience!
I like using shared configurations for projects from the same divisions as they tend to ask for the same issue types, workflows, screens, etc. I create templates for said divisions and then use that for the shared configuration when they request a new project. The only issue I find with it, is that when they want to change one project, but not the others, then you may need to split off from the shared configuration.
Hi Gustav,
We use a mix.
In perfect theory, it'd be great to have templates for everything -- so I try to keep the backend as consistent as I can, and to push back on customisations.
But in reality, our legacy instance is stuffed with customisation, duplicate shared configurations, etc. It's an ongoing effort to cleanup technical debt. What I've found that sort-of works so far to is to:
I think the next step for us would be to setup Atlassian User Groups and sit down with stakeholders to discuss how they use Jira, what can simplified, and what they want to see improved.
Shared configurations can be great for maintaining a consistent backend--but I do caution that if the stakeholders disagree then it's easy to end up with duplicate-but-not-quite-the-same groups of shared configurations that confuse both stakeholders and administrators; e.g. silos enforced by Jira.
The one skill I wish I'd had more of going into my position was more tenacity -- but also accepting it won't be improved overnight.
Hopefully this gives you an interesting perspective!
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events