Do you want to be able to change Comment security defaults? Now you can
Do you want to be able to change Comment security defaults? Now you can
This plugin allows you to:
The Comment Security Default plugin does not work on JIRA mobile.
The defaults for comment security can be set globally, for all projects in Jira, or per project. The configuration that is used for an issue uses the following logic
Setting the configuration globally is optional. The defaults can also be set on a per-project basis (see Project Settings below)
Important: If you are wanting to use user groups in comment security then this needs to be enabled within Jira. To enable it you need to go to System -> General Configuration, click edit settings, go to “Comment Visibility” and select “Groups & Projects”
The global configuration can be found by going to the admin section Manage Apps -> Comment Security Default -> Config
The global configuration page looks like the example shown below. There are two different types of configuration: ones that are only valid for one or more user groups and a default configuration. You can have as many configurations as you like as long as there is a maximum of one default configuration.
In the example above there are two configurations, one for users in the jira-adminstrators user group and a default configuration, to cater for everyone else. The list’s order indicates the order in which the configurations will be checked (starting from the top and moving towards the bottom). There are icon buttons on the right-hand side to move the configuration up or down in the list, although the default configuration is always last.
Click on the Add button to add a new configuration and click on the pencil icon to edit an existing configuration. There are also icon buttons to duplicate or delete a configuration
Clicking on the Add button or Edit (pencil) icon will show the following page.
At the top of the edit configuration page is the Groups. If this is empty then the configuration applies to everyone (assuming an earlier configuration isn’t found first). You can also add one or more user groups to this list and the configuration will only apply to users that are in one or more of those groups.
Below the Groups field are four sections: Security Defaults, Color Comment Fields, Service Desk and Access Control. These sections can be expanded/collapsed by clicking on the section title.
The Security Defaults section has the following fields.
At the top of this area is a “When Default is Missing” field that says what to do when a default is not found. The defaulting of security roles is dependent on the role being available to the project and/or user. If the role isn’t present then the plugin will follow the rule defined in the “When Role is Missing” field. The options are:
Next, the user gets the option to specify defaults for comments when assigning an issue to a user, adding an attachment, editing an issue, linking issues, new comments, logging work and transitioning an issue to a different status.
For transitions, there is a general default security level and the option to additionally add per-transition default by clicking on the Add button. This will open the dialog shown below. Once a per-transition default has been added it can be removed with the delete button.
Comment coloring can be used to highlight if a comment is “Viewable to all users” or if restrictions have been put on the comment. Colors can be specified for background and/or border colors. An example of two different colored comment boxes is shown below.
If you want a configuration to apply to Service Desk then you need to make sure that the “Enable Security Defaults for Service Desk” is checked (that is the default for new configurations). It is possible to have some configurations active for Service Desk and others not.
There are a few options that are specific to Service Desk. These options are:
Access Control has three options:
The default security level can also be specified for each project. This allows for variations of defaults depending on the requirements of each project.
The project configuration can be found in the projects admin section under Comment Security Default.
The look and functionality of the project page are identical to the global configuration page so please see that section for details.
For defaults, the project configuration is always checked first. If there are no configurations that match the users’ groups and there are no default configurations then Comment Security Default will check the global configuration,
Comment Security Default supports defaulting values for Jira Agile (Greenhopper). The same comments are defaulted using the same settings as for an Issue.
Defaults are treated differently for bulk editing of issue or bulk transitioning of issues. For this functionality, we are unable to determine which issues are involved in the bulk update. All comments in bulk changes are shown as ???. This will force the user to set the security level if they enter a comment. If the global defaults for the transition and/or edit issue checkboxes are NOT ticked then the security is all users.
For coloring of the comment field, the global settings will be used. If there are no global settings then the coloring will not be set.
