Blog

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
titleUse Cases

So here are some usage examples with goals of this plugin.

Caution Box
titleUse Dry Run!

Use -DdryRun to check what will be executed and changed on JIRA without actually changing anything!

Section
titleAdd Versions

Run

Code Block
languagetext
themeMidnight
mvn smartics-jira:versions 

on a project to add the current version and the next micro, minor, and major version on JIRA.
For instance, if your project is currently in version 2.3.1-SNAPSHOT, running the above command will ensure that the related project (identified with the issue management in your project's POM) on your JIRA server will have versions 2.3.12.3.2 (next micro), 2.4.0 (next minor), and 3.0.0 (next major) configured. If any version already exists, that's fine. If not, it will be created.

See Update Versions for more details.

Section
titleSync Project

Run

Code Block
languagetext
themeMidnight
mvn smartics-jira:sync 

on a project to check the differences in name, description, and URL between this information in the POM and on the JIRA project.

Section
titleCreate dependent Issues

Run

Code Block
languagetext
themeMidnight
mvn smartics-jira:issues -DrootIssue=MYPROJ-1 -DprojectKeys=MYOTHERPROJ1,MYOTHERPROJ2

to create dependent issues in upstream projects. This is useful if a change in one project has positive effect, like fixing a bug or adding a new feature, without the other projects needing to be touched.

Note Box
titleIn version 0.2.1: Local and global Parameter Names

Note that each parameter you specify on the command line may be made unique with the prefix smartics-jira (e.g. smartics-jira.projectKeys) with the next version of this plugin.

To keep the command line short, the prefix is not necessary.

...