Hi,
I would like to create issues for internal use only that can be connected to an organisation. The issues should only be viewed and edited by internal users. External users should not even be notified about the issue being created.
In addition, I would like to be able to connect the issue to a certain organisation. I want to be able to view all issues related to an organisation, both the once that are created for internal use and the once that are created by the customer.
Is there any solution for this?
Welcome to the Atlassian Community!
jira-servicemanagement-users-mysite
group or specific project roles like "Service Desk Team").ORG-NAME
") of type Select List (single choice) or Label.ORG-NAME
" custom field to link the issue to an organization.("Organizations" = "Organization A" OR "ORG-NAME" = "MyORG")
Hope this helps.
Thanks @Kishan Sharma
Is it possible to assign the Issue Security Scheme to certain Issues Types of the project? I would like the type of Issue to decide whether the issue can be viewed/edited/etc by the external customers or not.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Hanna Thunvall
In JSM Cloud, it is not possible to directly assign an Issue Security Scheme to specific Issue Types within a project. Issue Security Schemes are applied at the issue level rather than being tied to specific issue types.
However, you can achieve the desired behavior of restricting issue visibility or editability based on the issue type by using the following workaround:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Hanna Thunvall If my response was helpful, feel free to mark it as accepted; it can assist other users facing similar questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for a good suggestion and explanation.
I'm still looking into which alternative is best suited for our use case and have one follow-up question on the first guide you sent.
Step 1 - Point 3: Set Default Security Level for Internal Use Issues. How do I configure this? Can you guide me through what changes I need to make?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Hanna Thunvall If my response was helpful, feel free to mark it as accepted; it can assist other users facing similar questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.