-
Suggestion
-
Resolution: Unresolved
-
None
-
None
With our recent updates to unfurling, we require that users authenticate themselves with Atlassian, so that we know who they are and can guarantee they have access to the issue they are trying to unfurl.
Unfortunately, Slack Guest Users are unable to authenticate themselves because we require that the user authenticates with Slack, something guest users in Slack are incapable of doing.
It is possible for us to just authenticate the Guest User on the Atlassian side, although they won't be able to take any actions (via the "..." menu) or use slash commands to create Jira issues, as we won't be able to authenticate them on the Slack side.
This feature request is to support guest users to be able to unfurl via a secondary authentication method that does not exist and needs to be built
[API-180] Slack Guest User support for Unfurling
Has there been any update on this issue in the past year and a half? I manage product at a number of organizations, in some cases with multi-channel only access in slack, and cannot render an issue preview despite being the one who created the issue in Jira.
Any news on this suggestion?
We're having a lot of multi-channel guests that have access to Jira, but now the Slack app can't even be enabled for the multi-channel guests.
Would be nice that we could still keep using the multi-channel guests, instead of creating full time members to our slack. Just for the sake of the Jira Cloud - app.
Hey everyone,
Thanks for hanging in with us on this one. We have done a couple things over the last few weeks that should help alleviate the pain while we work out a more permanent solution to this (i.e. letting guests link their account so we can handle link previews for them in an authenticated and secure manner).
- Our first step was to add in a Not Now button, once you have seen a few login prompts you will now get a button that lets you snooze those prompts. We will check back in and prompt you again in the future but at increasing intervals over time, we don't want to be annoying but we also do want to allow people to login once there is a better opportunity and reason to do so.
- As of this morning guests should no longer be receiving login prompts for issue links. This was confusing and frustrating to our guest users. We had hoped we could just make it work. Rather than continuing to hassle guests with a prompt that won't work we decided to just suppress it for now. We will continue to work to bring this functionality back to all of our users, but in the meantime enjoy the silence.
We will continue to update this ticket as we make progress, again thanks for your feedback and patience with us.
Noticed today that the unfurling message at least lets you Snooze these notifications! Nice progress. Thanks for listening so far.
Agree with all the above, but additionally: please do not show the "To show a preview of this issue please log in to the Jira for Slack app. By logging in, you’ll be able to create Jira issues from Slack, set up notifications for your Jira projects into channels, and quickly take action on notifications." message to guests, at least until this issue is fixed, as it leads to a dead end that doesn't explain the problem and causes confusion.
Yes, can you please allow Slack Guest Users to do this? It’s quite critical for contractors or part-time employees in today’s ever-changing landscape of distributed workers
Users with Slack accounts and Atlassian accounts should be able to authenticate, regardless of guest status. Authorization is authorization. Please restore this functionality.
Talking about tickets today with my project manager. Every mention of a ticket number produces this warning. Very frustrating. Please address this.
Any movement on this ? It's been a bit and is pretty frustrating