The "changelog" command

[aik099]

The changelog command would:

• accept project_name required argument
• would validate via JIRA REST API that such project really exists
• get all resolved/closed issues for a project with Fixed resolution
• group them by "fixVersion" version
• sort groups (1 group = 1 release) by their release date in descending order (latest released on top)
• within each group (version) group issues by Change Log Group custom field value
• use value of Change Log Message custom field of each issue to generate a CHANGELOG.md file according to http://keepachangelog.com/ format

Arguments:

• version - allows to specify version or version range (e.g. 5.2.1 or 5.2.x)

Options:

• --dump - will create CHANGELOG.md file (when version is specified) or CHANGELOG_X_Y.md (when version range is specified); when not specified output will happen to screen
• --include-component - would list component of each task in changelog

[aik099]

Tricky use-case at In-Portal:

• the JIRA task is created for In-Portal project
• commits made in this task affect repositories associated with other projects (e.g. method added in In-Portal and some of modules makes use of that method)
• the module change log needs to have a note about it with likely a different change log message, but since task is in In-Portal project only it won't

Creating a sub-tasks for different projects might seem like a good idea at first, but in reality that would be a mess to maintain and test because patches from all associated tasks needs to be applied to test one task.