Slack integration : Jira previews, Transtion/More actions do not work

[Evan Yoo]

Hi, I was wondering if anyone is having similar problem with Slack integration regarding 'jira previews' and 'More actions' functions on issue creation notification. 

■ Here is the status. 

- Jira Cloud is invited to the slack channel

- The channel is connected to 'issues from site ****.atlassian.net' (**** = my company)

- When /jira unfurls, 'issue previews' are 'on' 

- /jira create command is working fine, /jira previews do not.

  (There is no interaction when I type issue key in capital ex) ISSUE-*** )

- On the bottom of issue notification created using /jira create,

   'Transitons' is working fine but 'Assign' and 'Comment' does not work. 

- I doubt the way of connection to be the cause of problem as I looked up other channel

  which works fine and found out the other channel is connected to 'projects' and not

  'issues'

- question is, in the other channel all other function works just fine(even though it's 

   connected to 'issues' and not 'projects' ) but when using /jira create commands to create 

   issues it does not print out 'truncated notification' even though issue is created on Jira.

- I am completely lost on how to connect specific slack channel to specific jira project and 

  be able to use jira commands and get notificaiton and to be able to use 'more actions' 

  buttons. 

■ Troubles

1) Issue previews command not working

2) 'Assign', 'Comment' actions not working

[Анна]

Hey Evan, this actually might line up with a permissions quirk I've seen mentioned before with how the Slack integration works under the hood.

The Jira-Slack app runs through a special system role called atlassian-addons-project-access, and for things like Transition, Assign or Comment to actually go through, that role needs Browse Projects permission in the permission scheme for whichever project the issue belongs to. On your channel that's connected to a project directly, that access is probably already there, which would explain why everything works fine there. But on the other channel where it's hooked up more at the issue or notification level, that role's access isn't always guaranteed the same way, and that could explain the truncated previews and the dead buttons you're running into.

Worth asking whoever has admin rights on your Jira site to check the permission scheme for that project and confirm atlassian-addons-project-access actually has Browse Projects checked. If it was never added there, that's very likely it.

Might also help to just disconnect and reconnect the Slack app for that channel once the permission is sorted, sometimes it needs a refresh before it picks the change up.

Hope that points you somewhere useful, let us know how it goes.