<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Fred Deichler on Medium]]></title>
        <description><![CDATA[Stories by Fred Deichler on Medium]]></description>
        <link>https://medium.com/@fred-deichler?source=rss-ff18ace4147c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kk-6Z_iO7Q8KChy1LORn6A.png</url>
            <title>Stories by Fred Deichler on Medium</title>
            <link>https://medium.com/@fred-deichler?source=rss-ff18ace4147c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:57:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fred-deichler/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Jira Automation — A Tool to improve Individuals and Interactions — Part 2]]></title>
            <link>https://fred-deichler.medium.com/jira-automation-a-tool-to-improve-individuals-and-interactions-part-2-499b0b672272?source=rss-ff18ace4147c------2</link>
            <guid isPermaLink="false">https://medium.com/p/499b0b672272</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[jira-automation]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[asynchronouscommunication]]></category>
            <dc:creator><![CDATA[Fred Deichler]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 16:36:40 GMT</pubDate>
            <atom:updated>2021-03-09T14:21:06.012Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jira Automation — A Tool to improve Individuals and Interactions — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vy1fbgG4KWd5C8dCJ3U0Qg.jpeg" /></figure><p>Hello, my name is Fred Deichler and I’m a Scrum Master at Field Nation. This article is Part 2 of my efforts to expand our automation that supports asynchronous communication.</p><p>If you have not already done so, you can catch up on the story of how I got to this point in <a href="https://medium.com/@fred.deichler/jira-automation-a-tool-to-improve-individuals-and-interactions-part-1-cf46f1a9c09b">Part 1</a> or you can forge ahead.</p><p>During Part 1 I discussed how Jira Automation could improve our workflow and provided 4 examples of how we were doing it. This article outlines 4 additional rules that show how an Incoming Slack Webhook can take asynchronous communication to the next level.</p><p>The rules in this article are</p><ol><li>Issue added to current Sprint</li><li>Priority in Jira has been escalated</li><li>Bug Created by the Triage team has been Updated</li><li>Daily Major Bug Reminder</li></ol><p>To start your Jira/Slack integration you 1st need to configure an incoming Webhook</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BEPY14hKbCX6dbsIBnCtGg.png" /></figure><h3>1. <strong>Issue added to current Sprint</strong></h3><p>The problem this rule is trying to solve is awareness and transparency of when an individual is adding a ticket to a Sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*DMlIJQ97exf-C9Z9tpSJKQ.png" /></figure><p>Utilizing the newly created incoming webhook (which can be used for every Jira Automation rule, as long as we specify the location in the Channel or user box) we are able to push the important information to the slack channel that is most relevant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Usaj0PTMKcY48wBQLTLfuw.png" /></figure><p>This is our 1st example of smart values, which allow us to serve the information we desire. As you see below we see</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*w1BTLJ55fGPe_hUtoyfHsA.png" /></figure><ul><li>{{initiator.displayName}} = the individual user who performed the Jira change</li><li>{{issueType.name}} = the issue type</li><li>&lt;<a href="https://company.atlassian.net/browse/%7B%7Bissue.key%7D%7D|%7B%7Bissue.key">https://company.atlassian.net/browse/{{issue.key}}|{{issue.key</a>}} {{issue.summary}}&gt; = this creates a clickable link with the issue summary in the link (be sure to substitute your Jira instance in place of company.atlassian.net)</li><li>{{issue.priority.name}} = the priority of the issue</li><li>{{issue.fields.reporter.displayName}} = the creator of the issue</li></ul><h3>2.<strong> Priority in Jira has been Escalated</strong></h3><p>The problem this rule is attempting to solve is an alert to the responsible team when the priority of an issue is raised from a Minor status to a Major status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*PvkXOlf15Zo9SSH4y7CMDg.png" /></figure><p>Because this is a Major issue we add a bit more information to the post to Slack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZi9el22_3wlkvIuurynOA.png" /></figure><ul><li>{{#issue.labels}}{{.}}, {{/}} = this joins any labels that are on the Jira ticket with a comma</li><li>{{issue.description.abbreviate(300)}} = this captures the first 300 characters of the description, it is important that we abbreviate this as failure to do so can (and did) cause a very large message to be posted to Slack</li><li>{{issue.comments.last.body.abbreviate(300)}} = the last comment posted to the ticket (also abbreviated)</li></ul><p>Those with a keen eye will have noticed that this rule actually sends 2 Slack messages and that is because Field Nation has a Triage team that would like to be alerted if one of the tickets created by them is escalated in priority. Discussions with our Triage team helped me create a shorter message that was more relevant to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pk-mrYT6HiwVUkB-CkDFmw.png" /></figure><h3>3. <strong>Bug Created by the Triage team has been Updated</strong></h3><p>The ability to alert our Triage team on a priority escalation caused another rule to be desired.</p><p>This rule alerts the Triage team if a ticket created by a Triage team member has started its journey through the development process. An important alert as it eliminates the need for the Triage team to explicitly follow-up on each ticket they create and the team does not have to rely on subscribing to each ticket in Jira and watch their email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*tI8Ke6d9OSJ3GBfvkbOV2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0eD69kqe9gIA67Gd0Ow37w.png" /></figure><ul><li>{{changelog.status.fromString}} = the prior status</li><li>{{issue.status.name}} = the new status</li></ul><p>And, how does it look in reality?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O9P3nXDvW7szjNvz90eShg.png" /></figure><h3>4. Daily <strong>Major Bug Reminder</strong></h3><p>With all the tickets flying around, sometimes bugs that are classified as Major don’t get noticed right away. I had a task on my calendar every morning to check for new Major Bugs that were not in a Sprint and I said to myself</p><blockquote>Can Jira &amp; Slack do this for me?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Q_H6Rgd7yxXrNHTeRtiD6A.png" /></figure><p>This rule uses a Schedule and a Cron expression to execute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3AD-N7kYoKam2OTJnp5COA.png" /></figure><p>At 7:45 UTC the following JQL runs and executes for each positive result and sends a Slack message to the appropriate channel to alert the team.</p><blockquote>(project = Ecosystems and type = bug and status = open) and priority in (Major,Blocker,Critical) and Sprint is EMPTY</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Ukw22AMGlf-WC9dTZiXwg.png" /></figure><p>With the rule in place, I couldn’t wait until the Cron job ran to validate its functionality, so I found that a team had 2 tickets that were Major and not in a Sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FaJOpz0iOCYFvQGTURhtEw.png" /></figure><p>So, there are 4 more rules to improve Asyncrounous Communication using the automation tools provided by Jira Automation and Slack.</p><p>I have 1 more rule that I’m going to share with you in Part 3 which takes demonstrated how all these rules can work together to quickly address production issues in a seamless fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*1TgrR3E0NI16W7bANGVStw.png" /></figure><p>Join me for Part 3</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=499b0b672272" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jira Automation — A Tool to improve Individuals and Interactions — Part 1]]></title>
            <link>https://fred-deichler.medium.com/jira-automation-a-tool-to-improve-individuals-and-interactions-part-1-cf46f1a9c09b?source=rss-ff18ace4147c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf46f1a9c09b</guid>
            <category><![CDATA[jira-automation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[asynchronous]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Fred Deichler]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 21:02:48 GMT</pubDate>
            <atom:updated>2021-03-08T16:37:41.524Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jira Automation — A Tool to improve Individuals and Interactions — Part 1</h3><p>A few months ago the Director of Software Engineering asked me what my goals were for the Agile Practice at Field Nation in 2021. After some reflection, I jotted down 2 items but felt like I needed a 3rd.</p><ol><li>Goal-Driven Sprints</li><li>Introduction of Calibration Sprints</li><li>…</li></ol><p>The 1st one is one that I had been working on coaching my Product Managers on for the latter part of 2020 and felt like we could make the leap in 2021.</p><p>The 2nd one was a pet idea of mine and my fellow Scrum Master to implement a version of an Innovation &amp; Planning Sprint into our process.</p><p>The 3rd one, well that was a question. What could I, as a Scrum Master of multiple teams that are spread over the globe do to improve our practice? We have a fairly solid implementation of Agile that embraces elements of many frameworks to create a version of Agile that works for us. We experiment with our software and our process quite regularly to embrace the power of iteration. But, what could we do to take it to the next level?</p><p>Without much more thinking I wrote:</p><blockquote>Expanded automation that supports asynchronous communication</blockquote><p>During a review with my boss, the CTO, and he said</p><blockquote>I’m not sure what that even means</blockquote><p>My response was</p><blockquote>I’m not 100% sure yet, but I like the way that it sounds and I think that there is something here.</blockquote><p>Fast forward to the present and I am not sure of what the measure of success for this goal is or what the final 2021 version of it will be, but it starts with embracing the tools that we have to provide individuals with the information that they need to be successful without them asking for it or needing to remember to explicitly provide it.</p><p>The 1st implementation of this for us is <a href="https://www.atlassian.com/software/jira/features/automation">Jira Automation</a>.</p><p>Our Software Delivery department consists of 7 Engineering teams, a Site Reliability team, a Data team, and a Triage team, each with a separate Jira project. Every team has a portfolio of features and microservices that they are responsible for, that all work together as a part of the Field Nation platform. To add to the complexity, these teams are spread across multiple timezones with minimal overlap in work time. Throw in Covid-19 and this was all leading to a potentially longer development cycle and reacting slower to the needs of our customers.</p><p>So, where does Jira Automation come into this? Well, I’m going to share with you the automation rules that I have set up for Field Nation and the problems each is hoping to solve.</p><ol><li><strong>If the Sprint field is Empty and Progress starts, add the ticket to the current sprint</strong></li></ol><p>The problem this rule is trying to solve is when individuals start working on tickets in the backlog (or a future sprint) and it is not transparent to the rest of the team through the Sprint Board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*VD05KqD5JEO9BFZlDLaA6A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*o19H0R2UqQCbUC8Dc3SCBg.png" /></figure><p>Due to there being 10 Jira projects running in parallel, I had to make the scope of this rule as a Single project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*xoNTfq7UCV6wVRW9pAHZZg.png" /></figure><p>We can tell it is working by examining the Activity History in the Jira Ticket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*6VK23FrITwRedfK5HO5rZg.png" /></figure><p>2. <strong>Link issues when mentioned in a comment</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*bOCy240rG6t6_2_pSG8u8w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*5teXRP6YQojQouyUC1Su6w.png" /></figure><p>The problem this rule is trying to solve is bringing transparency by relating tickets in Jira that are explicitly mentioned in a comment. I have also improved on the <a href="https://fieldnation.atlassian.net/plugins/servlet/ac/com.codebarrel.addons.automation/cb-jira-automation-rules">Atlassian suggested implementation</a> as this prevents creating duplicate links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/489/1*bdGfqnA2hFARePE3DSQFBw.png" /></figure><p>This rule still has some room for improvement as it errors out if the comment references the ticket itself</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77bHlxIu02fgkUBQRRIR7Q.png" /></figure><p>The occasional errors do not outweigh the value created when the rule works as expected.</p><p>This lead to the 3rd rule I implemented which is aimed at the Description field in Jira.</p><p>3. <strong>Link issues when mentioned in the description</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*wKuKzpUyLmEV3bCHsURPLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*fuhGNFN0qgw2Z7cXDUgZDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*DQBqr3qZDln-e2-Lv7aGiA.png" /></figure><p>4. <strong>When an issue closes, comment on the linked tickets</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*MUU25MNSmhKh90n5hnDfCQ.png" /></figure><p>The problem this rule is trying to solve is to even be more explicit with communicating relationships between tickets. Many times in my career, I have observed situations where a ticket from one team is blocked by a ticket from another team. Eventually, when the blocking ticket is complete, the blocked ticket does not progress without intervention.</p><p>This rule creates a comment on all related tickets when a ticket closes removing the impediment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*3ERGNcAD2evX4KrdskNObg.png" /></figure><p>At this point, I was feeling pretty good about our use of Jira Automation and didn’t foresee creating new rules. But, then we noticed that our Jira &amp; Slack integration was not working to alert us of newly created tickets and I set about creating more robust rules that utilize an incoming Slack Webhook URL.</p><p>Stay tuned for <a href="https://fred-deichler.medium.com/jira-automation-a-tool-to-improve-individuals-and-interactions-part-2-499b0b672272">Part 2</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf46f1a9c09b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>