How to get started - Admin guide

Owned by Manne Kjærby
Last updated: Sept 29, 2023
4 min read

In order to successfully utilize this product, it is imperative that you fulfill the following prerequisites:

  1. Jira Service Management for Cloud: Ensure that your Atlassian Site has a subscription to Jira Service Management for Cloud, as this product is designed to seamlessly integrate with this platform.

  2. Licensed Jira Service Management User: To access and fully benefit from this product's capabilities, each user must possess a valid license for Jira Service Management. This ensures that you have the necessary permissions and access rights to leverage its functionalities.

These prerequisites are fundamental to ensuring a smooth and efficient experience with our product. Please ensure that these requirements are met before proceeding with implementation. Should you have any questions or require assistance, our support team is readily available to guide you through the process.

 

Welcome on Board and thank you for using Organization Notes for JSM Cloud

Initially, navigate to the App administration page to configure the desired behavior for the application. For instance, determine whether it should function as a read-only entity within the agent view, entirely concealed or open for the agents with no restrictions.

Click on Apps >> Manage your apps >> Organization note - Admin Page

Here you find Global Setting, Organizations from where you can edit them, Organizations Custom field sync and our support options.

Global Settings

On the global settings tab, you have some options to control the behaviour of the app.

  1. View-Only Issue View: Activate the "View-Only Issue View" feature to control access to organization notes and details within the Issue view. This setting restricts users from making edits, ensuring data integrity and security.

  2. Edit Note Only: Grant agents the ability to edit organization notes exclusively while preventing any modifications to other details. This feature allows for focused and controlled updates to organization-related information.

  3. Hide Organization Note in Issue View: Enhance privacy and streamline your workflow by enabling the option to conceal the organization note from the issue view. This ensures that sensitive information is kept confidential when viewing the issue.

  4. View-Only Project Admins: Restrict edit access for Project Admins to organizations on the organization/customer page. By enabling "View-Only Project Admins," you maintain control over who can manage this critical information, promoting security and proper data handling.

 

Organizations tab

Here you can access & edit all organization notes. The admin will always have the option to edit organization notes and can’t be restricted. So if edit is restricted for project admins on the organization page and on the issue view for agents, then the admins is the only one that have access to edit organization details.

Organization Custom Field

The organization field normally have a default ID. The App are using this default id to retrieve and configure the organization data.

In cases where your cloud instance does not use the default organization field id, this function can be used to sync the correct field id.

Prior to utilizing this function, it's important to verify whether your organization's field ID differs from the default setting.

 

What’s next?

Read the How to Start - Agent guide to get a idea of how to use the app in daily work