<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>JIRA on Gary&#39;s Blog</title>
    <link>https://GaaraZhu.github.io/tags/jira/</link>
    <description>Recent content in JIRA on Gary&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>sec.gary@gmail.com (GaryZhu)</managingEditor>
    <webMaster>sec.gary@gmail.com (GaryZhu)</webMaster>
    <lastBuildDate>Fri, 20 Sep 2024 10:00:00 +1200</lastBuildDate>
    <atom:link href="https://GaaraZhu.github.io/tags/jira/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CRGenerator: automating Change Request documentation from git history</title>
      <link>https://GaaraZhu.github.io/crgenerator/</link>
      <pubDate>Fri, 20 Sep 2024 10:00:00 +1200</pubDate><author>sec.gary@gmail.com (GaryZhu)</author>
      <guid>https://GaaraZhu.github.io/crgenerator/</guid>
      <description>&lt;h2 id=&#34;the-problem&#34;&gt;The problem&lt;/h2&gt;&#xA;&lt;p&gt;Most regulated software environments require a Change Request before any production deployment. The CR needs a list of every JIRA issue included in the release — what changed, why, and who approved it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
