We want to see the templates you've created in Confluence! Edited

July’s community challenge is all about sharing pictures — and as an extension of our first post on what kind of templates you’ve created in Confluence, we thought we’d take this opportunity to actually see those templates!

Post screenshots below (feel free to cross out or remove any sensitive info) to show off your best templates and tell us how they’ve helped improve your work.

We can’t wait to see them!

*IMPORTANT NOTE: there is a known bugwith posting images in discussion comments if you try to post an image and nothing else, you get an error. You will need to include some text in addition to the image.

9 comments

Since we do not use JIRA Software yet for project management, we have developed project based global templates. These are not super fancy, but they supply us the information needed to do our job efficiently.

Here is the lates template I created. this is a "plugin evaluation" template. We always evaluate market place plugins before we install it in our confluence instance.

here we track user requirement that leads to get a plugin, any substitute plugins and nominated plugin/s for further evaluation based on our selection criteria, functional analysis, test scenario executed and results, technical analysis, anomaly report , risk found and finally a summary of tasks executed so far.

substitute plugins and nominated plugin/s for further evaluation based on our selection criteria (we usually consider about the Atlassian verification, user reviews and number of active instances at the considered time)

functional analysis (function list available)

test scenario executed and results (here we mention the test results of the functionalities after testing the plugin in our test instance)

I manually test. As it is just a evaluation (most probably one time thing) I think it is waste of time to script a automation test suit. 😊

Also even for a new 'plugin version evaluation for already existing plugin'; I refuse to script test suits since vendors improve and change the functionalities rapidly and have to change the code time to time. it is much much cheaper to test manually.

Here is my latest blueprint: Created to get Processing standards, we are using on all 15 production locations worldwide - digitized, centralized and unified.

To make it comfortable for the non-technical users - I used several variables (dropdown lists) to choose from. You can also see several Macros we used and costumized for this space that tracks who created the document, who worked last on it aso. sorry that everything is in german

We overworked it several times - and I have to say: it was absolutly worth the time we invested. People who first were skeptical love how easy they can create and update those important things. Acceptance is growing!

Totally agree: creating a really good template can be time consuming, but it's almost always worth it in the long run! At Atlassian, our templates save me *so* much time –– both because I don't waste time creating the same page formats over and over again and because our documents are standardized and easy to scan through for information.

I can definitely tell that you put a lot of effort into this template, it's so beautiful and well-organized! I especially like the dropdown lists and that you made an effort to make it accessible for non-technical users. Nice touch!

What is another benefit of well-prepared templates, which you work out well that are checked at regular intervals, is that people have to overthink their processes and claims they have to it. We found several points that had absolut first priority that are now gone and not needed anymore :)

It seems like a lot of you are fans of the expand macro when it comes to templates! I am too. I think it's really helpful when all or most of the major information in a template is available at a glance and viewers can choose if they want to read more detailed information. Not only does it make your document easier to read through, but I also think it's more pleasing to the eye.

This is my projects' summary page template. The scope of this page is to keep track and on the updates made on each project page and to have the info in a single place.

I used a table and each cell in Project name column has an expand macro/ and excerpt include (bringing here only the update info from the project page, where an issue macro is also present). Details here represents the link to the page. At the beginning, the header also had the sorting feature, which now is gone (no explanation found yet- no merges in the table). The sorting used to be very helpful :(.

The date for the last update is inserted manually and it would really be very helpful if anyone could suggest a macro that would help me just track the last update directly from the updated page. Any other suggestions are welcome.

Sorry to hear that you've been having trouble sorting your tables by date and thanks for your feedback on the heading sorting feature. Have you considered using the Advanced Tables for Confluence app? One of its features is advanced date sorting so hopefully it helps!

The template I use the most is the one for my Jira or Confluence tutorials:

Very simple but very useful:

I have one template for Jira and another one for Confluence so that it automatically adds the corresponding label (tuto-jira or tuto-confluence) to organize the main tutorials page by subject. I used to have only one template but I very often forgot to add the right label!

Goal is to describe the tutorial more precisely, e.g.: a tutorial is called "How to add swimlanes on a board?" and the goal is "Improve boards readability"

Prerequisites is to mention whether you need to be an admin, or the sprint to be finished for example

Subjects mentioned is to add keywords like JQL, board, workflow, etc.

And an anonymized screenshot of the main tutorials page to be complete:

We use Jira to track our IT assets (servers, workstations, etc). However, we use Confluence to document information about the services on our servers. We use Jira's functionality to link issues to Confluence pages. So, when we have a new service application we create a Confluence page for it and then in Jira we link the server ticket to the Confluence page. Also, any change tasks to the application or servers are linked to the Confluence page as well. I also created a couple user macros that wrap the confluence Jira macro to pull back tickets that are linked to the page that the user macro is placed on. One caveat this requires the ScriptRunner add-on as it uses a JQL function added by that add-on. Below is a screenshot of the template and the user macro code.

With this setup we have a page with a page properties report macro that rolls up all that information so we can see a list of our services, the critically, who owns the service, the server(s) that support that service, and vendor support information. So, in the event of service disruption we have a one-stop-shop for high level information about our service catalog. And if we drill down to a specific service we can see documentation for that service and any work done on it (upgrades, config changes, issue tickets) audited through Jira tickets.

Love to see so many people making use of how well Confluence and Jira can work together! I think your idea of creating a "one-stop shot" for service catalog info is such a good way to make sure you can get things back on track as soon as possible if there's a service disruption. So happy to see that you're using templates to do your best work!