Jira / Slack - Can it be read-only? Can we block interacting with Jira through Slack?

[Marta Zapatero]

We have recently migrated from Jira Server to Cloud.

We're interested in getting Jira notifications on Slack up and running again- the usual "new issue created, new issue assigned to you. you have been mentioned in this issue" etc.

But for security, data integrity, and user permission reasons, we want it to be A ONE-WAY CONNECTION. We want to disable ANY kind of interaction from Slack, such as changing the status or commenting on the issue. To interact with the issue, a user should click on the link in the message to open Jira and do it from there.

We know Atlassian ensures everything is secure, but our tech leads would much rather replicate the way Jira Server / Slack integration worked.

The Jira Cloud for Slack marketplace page mentions management settings, but it has no documentation about what options there are to manage permissions and interactions. 

So if anyone has that information, I'd be very grateful! 

PD: We're only allowed to use official plugins (either Atlassian or Slack), so third-party marketplace app suggestions won't do, no matter how cool they are :( 

[arielei]

Hello @Marta Zapatero 

In the project permission scheme remove the "atlassian-addons-project-access" role from the create work-item option.

[Marta Zapatero]

Thank you very much!

And would we be able to give different roles to different addons, or is it forced on all of them? We want Slack to have read-only access, but we may want Jenkins to update issues.