2 min read

Jira Tips: Create From Template vs. Create From Shared Configuration

By Katie Thomas on Apr 9, 2021 11:26:00 AM

Blogpost-display-image_Create from template vs. Create from shared configuration (1)

There are a variety of ways to create projects in Jira – whether from a predefined template from Atlassian or from a shared configuration with an existing project. As Jira administrators, this is one of the first questions you'll be faced with when onboarding new teams to the instance. Let's walk through the different strategies, and why we prefer creating from shared configuration. 

Creating from a template

Creating from the Atlassian templates will create a new set of unique schemes to that project - new items in your instance that are not shared with any other project. To create from a template, simply select one of Atlassian's predefined models on the 'Create Project' page. 

The benefit of using these templates is that each of your projects are self-contained, and a model has already been put together by Atlassian. Configuration is not shared with any other projects, even if everything is exactly the same. This means that teams can adjust their workflows, screens, etc. without affecting anyone else. This can be good for teams who don't share any processes with other teams using Jira, and allows project administrators more control over their projects. 

However, for organizations that are looking to scale and/or standardize, this can be a huge headache.

Creating from shared configuration

Using a shared configuration means that you are reusing existing and established configuration items in your instance. Rather than creating new sets of schemes when a project is created, you create based on another project. For example, if you created from shared configuration, both the old and new projects will use the same workflows, screens, and field configurations. Note that they won't share any Jira Service Management specific configuration items, like request types or queues. 

Additionally, once a project shares a configuration with another project, Project administrators can no longer edit the workflows without being Jira admins, which has the added benefit of supporting the goal of standardization and scalability in addition to administrative governance.

There are pros and cons to each of the above, but ultimately, it is recommended that whenever possible, projects should be created from Shared Configuration.

While templates allow teams to have more control over their projects, it does not lend itself to standardization or maintaining a clean Jira instance. Although IT teams often request more options for teams to self-service with Jira project configuration, in the interest of scalability, allowing any user to create their own Jira projects is not a best practice. Jira projects should not be treated as "projects", spun up or spun down on a regular basis: as a best practice projects should be long-lasting and consistent. Additionally, from an administrative perspective, it can be challenging to manage the sheer number of schemes and additional items when trying to troubleshoot issues or maintain the instance.

Looking for expert help with your Jira instance? Contact us, we'd love to help!

Topics: jira atlassian blog administrator best-practices tips
2 min read

Jira Administration: Sys Admin vs Jira Admin vs Project Admin

By Luis Machado on Mar 2, 2021 7:35:43 AM

Blogpost-display-image_Jira Administration- Sys Admin vs. Jira Admin vs. Project Admin2When thinking about Jira administration, or really administration of any software, project, or endeavor, the old idiom “too many cooks in the kitchen” often comes to mind. There’s a fine line between empowering your user base and setting the stage for mass hysteria and confusion within your instance. Fortunately Jira offers some out-of-the-box options to help with setting up boundaries for those users who need more control over the instance but keep them from wreaking too much havoc.

Admins

We’ll start with the bottom, Project Admins. There was a time in ancient Atlasssian historical records when those who were managing projects almost had to be System Admins as well. This was because the permissions needed to make necessary regular changes to the projects these individuals were maintaining required as such. Atlasssian has been improving upon this incrementally as of Jira 7. Since that update it is possible for Project Admins to add Components and Versions to their projects and even as of 7.3, expanded with 7.4, make adjustments to the workflow among other things. So if you’re evaluating your System Admin group and discover that many of the individuals are really only responsible for maintaining specific projects it would behoove you to re-assign those you can to the Project Admin role within the projects they are responsible and get them out of your kitchen.

The next level of administration is the Jira Administrator. Now this is where things can maybe become a bit confusing because the powers granted to that of the Jira Administrator are very similar to that of the System Administrator, but there is a very key distinction which we’ll explore. Those within the Jira Administrators group are not able to make changes related to the server environment or network. This would prevent them from making changes to things such as configuring mail server settings, export/import data to and from XML, configure user directories, as well as many more functions related to the system as a whole. Where this could be useful is delegating out some of the more regular tasks such as creating new projects, creating users, etc. This gives larger organizations a way to separate out the tasks without increasing the risk of potential hazardous changes to the application.

After having covered the last two, the final role should be somewhat obvious. The System Administrator permission is for the Grand Poobah of the Royal Order of Buffalos. This role allows unlimited access to all aspects of the Jira instance. It is recommended that only 1 - 3 people maintain this permission as needed. Again, the idea is to ensure that there is concise and regulated changes being made to the instance as well as accountability. With great power comes great responsibility. When in doubt, opt for the lesser of two evils when granting administrative permissions. You can always bump them up If it’s not serving your needs. Again, the goal is to empower your user base, not have them overpower you.

For question on admins, or anything else Jira, contact us, and one of our Jira experts will get in touch.

Topics: jira atlassian blog administrator best-practices

Jira Administrators Primer

By Praecipio Consulting on Sep 10, 2014 11:00:00 AM

Want to learn more about effective Jira administration? This Jira Administrators Primer will cover tasks and best practices that every Jira administrator should know. Delivered by our very own Christopher Pepe, attendees from this session will help you become more proficient in maintaining your Jira instance.

Please contact us for more information or take a look at our other webinars.

Topics: jira administrator training webinars
2 min read

From Atlassian: Finally, Bitbucket Supports Git!

By Praecipio Consulting on Oct 3, 2011 11:00:00 AM

Bitbucket now supports Git!

You’ve been asking for it, the Bitbuket team has even joked about it – now it’s here (for real): for the one year anniversary of Bitbucket joining Atlassian, they’re announcing Git support.

All your source, all in one-place
Whether you are using Hg or Git, you can now keep all of your code in one place with your preferred DVCS format. If you have existing code you would like to migrate, you can easily import your Git, Mercurial or Subversion source code. Atlassian’s added a new importer for GitHub to our existing site importers which include SourceForge, Google Code and Codeplex.

Unlimited private and public repositories
A big advantage for Bitbucket users is the ability to have unlimited private repositories for free. This means you can store every line of code you’ve ever written in one place without paying a cent.

Notable Changes

UI improvements have been happening gradually over the past six months:

  • Commit and file history browser
  • Source viewer
  • Issue tracker browser
  • Project downloads

Today’s release includes a new UI for the repository and user administration pages. A never-ending goal is to make Bitbucket easier to navigate and use the operations you need fast.

Get your Git on

Pull requests, code commenting and key integrations with developer tools (Jira, Flowdock, HipChat, Twitter, Bamboo, Jenkins and more) have made this a feature filled year. And now Atlassian adds Git…

If you haven’t checked us out lately, Bitbucket has had a year of record growth – more than tripling the number of accounts since the acquisition, adding over 350 improvements, bug fixes and new features. Sign up now (no credit card required) and get unlimited private repos for free!

Were do I find the latest updates about Bitbucket?
Visit the Bitbucket blog at http://blog.bitbucket.org.

Topics: jira atlassian blog administrator bitbucket bamboo distributed-version-control-system google hipchat repositories twitter support developers git coding
2 min read

Atlassian: SharePoint Gets Social With Confluence

By Praecipio Consulting on Jun 7, 2011 11:00:00 AM

The latest release of the Atlassian’s Confluence SharePoint Connector is loaded with new features that turn SharePoint into the social collaboration platform you always wished it was. Best of all, it’s available for download today…here’s the scoop:

Unlock Documents and Lists stored in SharePoint
With Atlassian’s redesigned SharePoint list macro, anyone can insert their favorite SharePoint lists into Confluence without needing to know wiki markup.

1. Smarter SharePoint List Macro
New ‘Smart Fields’ for the ‘SharePoint List Macro’ in the Confluence ‘Macro Browser’ make light work of finding your ‘Lists’ from SharePoint and embedding them into a Confluence page for others to see.

2. Custom SharePoint List Views in Confluence
We’ve also made it easy for users to reuse the custom list views they’ve configured in SharePoint. Getting your personalized SharePoint experience in Confluence is now just a couple of keystrokes away.

Bring Social Collaboration into SharePoint
Experience the collaborative advantages of Confluence inside SharePoint like never before with new social features for SharePoint users.
1. Bring Confluence Blogs into SharePoint
A new Blog Post Web Part lets you bring the rich discussions and newsworthy content shared in Confluence, into SharePoint. And, with the power of Web Part Connections, you can connect a Blog Post Web Part to the new Blog Post Tree View Web Part. This lets SharePoint users browse all the blog posts in a Confluence Space directly from SharePoint. Now everyone can stay-up-to-date on the important announcements published in your intranet.

2. Post comments on Confluence content from SharePoint
Users can now make comments on the Confluence pages and blog posts they consume in SharePoint allowing more people to contribute to the conversations taking place inside your Confluence wiki.

For Administrators…
One-step Farm-wide Settings
We’re always striving to make the life of administrators easier. In this release we’ve added a huge time-saving feature – connecting your entire SharePoint farm to Confluence is now single-step process. Now when you add more SharePoint sites to your Farm, they’ll be automatically connected to your Confluence wiki.

Available Today!
There are even more improvements in the SharePoint Connector 1.4. Go get it, try it out, and let us know what you think. Check out the release notes here, or go ahead and download!

Topics: atlassian blog administrator confluence release sharepoint wiki collaboration download integration macros

Praecipio Consulting is an Atlassian Platinum Partner

This means that we have the most experience working with Atlassian tools and have insight into new products, features, and beta testing. Through our profound knowledge of Atlassian environments and their intricacies, we can guide your organization as you navigate these important changes.

atlassian-platinum-solution-partner-enterprise

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us