Policy

Purpose and Use

Objective: The "Extended JSM Portal" plugin is designed to enhance the functionality of the Jira Service Management customer portal by allowing project administrators to add, configure, and display additional fields. This policy ensures the effective management and use of the plugin.

Usage Guidelines:

  • The plugin should be used to improve information visibility and customization in Jira Service Management.

  • Administrators are authorized to configure the plugin to add or remove fields based on project requirements.

  • All users are encouraged to utilize the added fields to optimize their workflow and information access.

Data Integrity

Accurate Configuration: Ensure that all configurations and field additions are accurately implemented to reflect the true needs of the project and maintain data coherence.

Avoidance of Redundant Data: Avoid creating duplicate fields that could lead to data redundancy and confusion among users.

Data Privacy

Sensitive Information Handling: Avoid using sensitive or personal information in the additional fields unless it is essential and authorized. Ensure compliance with data privacy regulations when handling such data.

Access Control: Implement strict access controls to ensure that only authorized personnel can alter the plugin settings or access sensitive field data.

Compliance

Adherence to Organizational Policies: The use of "Extended JSM Portal" must comply with the existing policies and procedures of the organization, especially those related to software enhancements and data handling.

Data Protection Compliance: Ensure that all data handled by the plugin is in strict compliance with relevant data protection laws and regulations to safeguard user information.

Monitoring and Audit

Usage Monitoring: Regular monitoring of the plugin’s usage to ensure it is used in compliance with this policy and does not compromise the integrity of the Jira Service Management system.

Audit Trail: Maintain a clear and comprehensive audit trail of all changes made using the plugin to ensure accountability and traceability.

Modification and Removal

Change Management: Follow a structured change management process for any updates or modifications to the plugin, ensuring that all changes are logged and reviewed.

Decommissioning: Establish protocols for safely decommissioning and removing the plugin or any of its components when they are no longer needed, ensuring that all associated data is securely handled.

Â