Our Jira project (let’s call it project A) is connected to the Jira project from External-Customer (lets call it project B). They create a ticket and exalate it to us, creating a new ticket on our project A. However, we do not want them to be able manually connect to existing tickets on project A, because that would give them access to confidential information from pre-existing tickets, tickets that we do not want to sync. Is it possible to set up such restrictions with Exalate?
Majid
2
@German_Lesch are these both Jira Cloud instances connected to each other via Exalate or Jira DCs please?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Can Exalate be used on 2 different customers' Jira instances to sync only specific scopes, without compromising/exposing the security of any other "project" they don't want to sync on both sides? Any other project must be unavailable from the other party | 1 | 24 | November 4, 2024 | |
| To be able to view/see the content of the Jira Tickets of one instance in the other nor vice versa | 1 | 13 | November 4, 2024 | |
| Is it there a way to allow sync from single Jira project only? | 1 | 68 | November 4, 2024 | |
| Jira On Premises to jira cloud integration | 2 | 56 | November 4, 2024 | |
| From Zendesk Exalate to multiple issues in Jira On Prem | 1 | 33 | November 4, 2024 |