Using will prefix the deployment plan’s name with today’s date which helps for default sorting. The only customisation I use here is for Template Name. Deployment Plan Overviews Create Deployment Plan: Create from Template Macro Otherwise it won’t show up in our report. It’s important that our template has the deployment-plan label added by default. The default query I set in the template looks like this: project = PHO fixVersion = 'XXX' AND labels = deployment-steps ORDER BY priority DESC Labels I prefer to have a separate field but if that is not an option you can do things like putting them in a comment with a bold Deployment Steps title The deployment steps should then be recorded in the ticket.Any JIRA tickets that require manual deployments need to be tagged with deployment-steps.If they maintain any manual steps within the related ticket(s) everything is moved as one. I like to use this technique to track manual steps because if developers are continually adding manual step to a deployment plan, then their feature is not included in the release, they need to come back delete and move it. The query I set by default: project = PHO fixVersion = 'XXX' ORDER BY priority DESC Manual Steps: Jira Issue/Filter Macro These are more reliable than just referencing a sprint or tickets directly. I recommend using Fix Versions in JIRA to track your deployments. Description of Change: Jira Issue/Filter Macro Step 1: Identify the key details It's essential that anyone who comes to your release planning page can quickly identify who is involved, and what the goals and expected outcomes are. a match for your project in Confluences extensive template gallery. Follow these steps to create an awesome release planning page. But you can see how the template helper text will be valuable as this deployment plan moves through each environment. Confluence Cloud As Your Newest Project Manager Lets explore both the power and. In the template I include all the valid statuses of a deployment plan for reference. This is what will allow us to produce the deployment plan overview report. Page Properties MacroĪt the top of the page we need a Page Properties Macro. I will only talk to the key configuration elements here. It will ensure that the authors of these templates know what values they should be using / what is expected in each section. I can’t stress enough here how valuable it is to use the Templates helpers. If you can’t, create a blank page that can be copied each time. To ensure this is a repeatable process create a template in Confluence for this page. Deployment plans are an essential part of Software development but if you ask any developer to actually do one expect to see some eyes rolling! This article details the templates that I regularly use in Confluence to make this process easier to manage and report on.
0 Comments
Leave a Reply. |