Page Comparison

The plugin uses JIRA's own versions, so no magical version field is created. The add-on allows mapping of more than one component to single version. For example you can map both component Android and component iOS to version 1.0. If you check JIRA's own Version Tab, there will be one version 1.0. But you can also create more than one version 1.0 with suffixes like 1.0-android and 1.0-iOS. In that case you can map component Android to version 1.0-android and component iOS to version 1.0-iOS. This schema some certain advantages. In this case, release status and release date fields are kept in sync with JIRA's own version definition. That is, modifying version's release date and release status in the plugin also modifies JIRA's version definition and vice versa. If a version is used by multiple component changing the version's release date and status from the plugin does not change JIRA's version definition. Because in that case there will be more than one release date and status for a version for each component. For example release date and status for Android Apps's version 1.0.0 may be different than iOS App version 1.0.0makes relationship between a version and a component more explicit and even if you uninstall the add-on in the future, you can still see which versions are used for which components.