Message-ID: <750260079.13346.1711647860575.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13345_178347276.1711647860575" ------=_Part_13345_178347276.1711647860575 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Some features in Structure are designed as modules and can be sa= fely turned off. You can do so to remove unnecessary functionality, or limi= t the exposure of Structure plugin to the users.
If your aim is to limit the exposure of Structure, consider restricting = permissions to specific groups of users - see Gradual Deployment.
While it is easy to disable a Structure module, we don't recommend to to= uch any modules except those listed in this article to ensure stability of = Structure and your JIRA application.
To turn off a module:
You can always turn the feature on later by clicking the Enable button.<= /p>
Feature |
Module name |
Effect of disabling this module |
---|---|---|
Activity Streams |
|
Activity streams provider and Structure-relat= ed updates are removed from the following places:
|
|
Structure section is removed from the issue p= age. |
|
|
Structure tab is removed from the issue detai= ls panel on the Agile board. |
|
|
Users will not be able to install synchronize= rs, and installed synchronizers won't run. You will need to restart the plu= gin to have settings make full effect. (Disable plugin, then enable plugin.= ) |