Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-16450

JIRA summary description should be used for changelog creation


    • Type: Suggestion
    • Status: Resolved
    • Priority: Not specified
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Documentation
    • Labels:


      I was looking through several changelogs, trying to find when a particular issue was fixed and released, but I did not know specifically which JIRA ticket it was.

      I was searching the changelogs by keywords that I was hoping to find that might have gotten me a hit, but was coming up empty.

      I instead searched the JIRA issues to find the match, and then was able to determine the Fix Version, but it would have been nice to be able to do the same within the changelogs.

      It appears that this is somewhat inconsistent – some changelog descriptions match the JIRA summaries exactly (or very closely), while others do not at all. In a brief discussion I had with Lorraine Chapman, she indicated that the changelog descriptions are derived from the pull requests.

      Here's the specific example that caused me to ask:

      Plugins | HPCC-15952 Execute void transactions up-front

      Whereas that JIRA summary is:

      EMBED code for MySQL not working after upgrade to 6.0.2


      Not a huge deal, but having consistency across these would be beneficial.




            • Assignee:
              richardkchapman Richard Chapman
              kev77log Kevin Logemann
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created: