...
You have the option to change the Encryption String. This string is like a secret code used to protect your sensitive information (email, API token, and visibility settings). It's highly recommended to personalize this string to enhance security.
Note: For a detailed explanation of how your data is stored and secured, click here.
...
The diagram below illustrates how 'Assets Owner for Jira' safeguards your sensitive information in our database:
Initial Encryption: Your data (email, API token, Encryption String and visibility settings) is encrypted using the unique Encryption String you set in the Configuration Page. This adds a first layer of protection.
Secondary Encryption: The already encrypted data undergoes a second round of encryption using a secret, undisclosed string. This adds an extra layer of security.
Secure Storage: Finally, the double-encrypted data is safely stored in our database, ensuring maximum confidentiality and protection against unauthorized access.
...
Note: Remember to save your configuration by clicking the 'Save Configuration' button before moving on.
Step 4: Configure Visibility Settings
Optional but Highly Recommended: While this step is optional, it's crucial for tailoring the app to your specific needs. Take a moment to configure these settings to ensure the app works exactly how you want it to.
...
Which groups are allowed/restricted to access “My Assets”
The first thing you'll see is a multi-select box where you can choose specific groups from your Atlassian instance. Use the 'Allow/Restrict' toggle to determine whether the selected groups should have access to the 'My Assets' menu or not.
Allow: The selected groups will be able to see the 'My Assets' menu.
Restrict: The selected groups will be prevented from seeing the 'My Assets' menu.
(See the image below for a visual representation.)
...
Which Asset-Schemas should be hidden from “My Assets”
The second multi-select box allows you to choose which Asset Schemas, from your Jira Servicemanagement instance, you want to exclude from the 'My Assets' menu. Any schema you select here will not be displayed in the 'My Assets' menu. This helps you filter out irrelevant schemas and keep the menu focused on the most important asset types.
(See the image below for a visual representation.)
...
Which Object-Types should be hidden from “My Assets”
Finally, you can fine-tune the 'My Assets' menu by selecting which Object Types to exclude for each Asset Schema.
Important: If you've already excluded an Asset Schema in the previous step, its corresponding Object Type selection will be grayed out, indicating that it's inactive. This visual cue helps you keep track of your choices.
(See the image below for a visual representation.)
...
Congratulations! You've successfully configured 'Assets Owner for Jira'. Click the 'Save Configuration' button, and you're all set! Your app is now tailored to your specific needs.
Important: After changing the group permissions (Allow/Restrict), you need to reload your Jira instance for the changes to take effect. Other configuration changes will apply immediately without requiring a reload.