Date: Thu, 28 Mar 2024 09:20:31 +0000 (UTC) Message-ID: <2144139578.101.1711617631768@e8054a1f1b3a> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_100_1786017059.1711617631768" ------=_Part_100_1786017059.1711617631768 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
One of the main goal of the plugin is having as little affect on your JI= RA instance as possible. Some day if you decide to uninstall the plugin you= can continue to use JIRA as if the plugin has never installed. All your ve= rsions and components will be available only they will not be component spe= cific and there won't be any bundles of course since these are provided by = this plugin. The plugin uses your original component and version defi= nitions. You can define your components and versions as usual. Your previou= sly defined component and version definitions are also fine, you can use th= em.
Secondly you don't need to use component specific version for every proj= ect but you don't need to do anything special to enable or disable plugin p= roject by project. If you don't define any component specific versio within a project'= s administrative section this project continues to work as if plugin is not= installed. Even if you define one component specific version, the plugin i= s enabled for that project. For other areas there are similar opt-out mecha= nisms exist in the add-on settings.
Plugin provides 5 major functionality: