We want to see the templates you've created in Confluence!
10 comments
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.
Before each release, we will create a Issue for approval in Jira, and the specific content of this release will be reflected in Confluence, linking the Jira and Confluence pages through Issuelinks
What a nice idea @Jessica Lynn
Excited to see how others work.
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!
Hey Atlassian Team Members, how about you show us some of your secret / non-published templates!
Here's one that we use to report on the status of large projects.
Each large project gets its own Confluence space with a templatized homepage
The deploy date is reading from a Jira fixVersion date using a custom macro
The status is a custom macro that has pre-defined statuses
All projects get aggregated by team on a single project status page using page properties report macros. More info can be accessed using the expand macro
Thanks @Joshua McManus!
Here is a little clip of the macro in action:
And the result:
Code is open source here: https://github.com/msolomonTMG/confluence-jira-deploy-dates-add-on
Hello!
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.
Hope this could prove helpful for someone :)
Thanks for other inspirational ideas found here!
July
The template I use the most is the one for my Jira or Confluence tutorials:
- 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.
Macro Name:
jira_server_links
Macro Title:
Jira Server Links
Macro Body Processing:
No macro body
Template:
## Developed by: Davin Studer
## Date created: 06/28/2018
## @noparams
<ac:structured-macro ac:name="jira" ac:schema-version="1">
<ac:parameter ac:name="server">{Our Server}</ac:parameter>
<ac:parameter ac:name="columns">summary,Production Status</ac:parameter>
<ac:parameter ac:name="maximumIssues">1000</ac:parameter>
<ac:parameter ac:name="jqlQuery">project = ASSETS AND issuetype = Server AND status = "In Service" AND issueFunction in linkedIssuesOfRemote("query", "pageId=$content.id")</ac:parameter>
<ac:parameter ac:name="serverId">{serverid}</ac:parameter>
</ac:structured-macro>Macro Name:
jira_issue_links
Macro Title:
Jira Issue Links
Macro Body Processing:
No macro body
Template:
## Developed by: Davin Studer
## Date created: 06/28/2018
## @noparams
<ac:structured-macro ac:name="jira" ac:schema-version="1">
<ac:parameter ac:name="server">{Our Server}</ac:parameter>
<ac:parameter ac:name="columns">key,type,summary,created,status,assignee,reporter</ac:parameter>
<ac:parameter ac:name="maximumIssues">1000</ac:parameter>
<ac:parameter ac:name="jqlQuery">project = OPSLOG AND issueFunction in linkedIssuesOfRemote("query", "pageId=$content.id") </ac:parameter>
<ac:parameter ac:name="serverId">{serverid}</ac:parameter>
</ac:structured-macro>
