nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way for a Jira Cloud admin to map Slack usernames manually?

Andrew Krigline

Per this issue, it looks like the new Jira Cloud Slack integration is ... frankly really difficult to onboard into.

Is there some way for a Jira Cloud admin to manually map Jira usernames to Slack usernames in order to avoid every user in the company Slack having to individually interact with this bot?

Accepted answers

Trevor Thompson

Hi @Andrew Krigline

The Jira Cloud Slack integration should be a breeze to onboard into. Yes, each user needs to authenticate the Jira for Slack app in order to interact with it in Slack.

Unfortunately, there's no way for an Admin to manually map Jira usernames to Slack usernames. All authentication is handled on a per-user basis. So users will have to authenticate themselves, but there is relatively low friction involved (first time they attempt to interact, they will be asked to log in, and the log in flow should only take a few seconds).

Let me know if you have any other questions or how I can help
Trevor Thompson
Product Manager, Product Integrations

All comments

Trevor Thompson

Hi @Andrew Krigline

The Jira Cloud Slack integration should be a breeze to onboard into. Yes, each user needs to authenticate the Jira for Slack app in order to interact with it in Slack.

Andrew Krigline

We recently converted from Jira-server to Jira-cloud. We had a home grown bot that combed messages looking for Jira Tickets and unfurled them. The bot was time consuming to maintain and one of the draws of Jira Cloud was the official Jira integration.

Thing is, convincing all 90 or so people in Slack to take the couple of minutes to mess with the Jira Bot integration is not as easy as it sounds. It would be about 500 times more efficient if one of our Jira admins could manage this mapping (one person's 30 minutes versus 90 people's 3 minutes, in addition to all of the interruption cost).

It would be better still if the official bot would do a basic unfurl for all channels it was part of if it didn't know who was who. It shouldn't need that information to just display the basics of the ticket?

IMO this would be a pretty big boon to the official bot's functionality. I'll happily submit feedback to this effect if you'll point me in the right direction.

Trevor Thompson

Hey again Andrew, thanks for the insights! They are insanely valuable.

>Thing is, convincing all 90 or so people in Slack to take the couple of minutes to mess with the Jira Bot integration is not as easy as it sounds.

Agreed! What functionality are you hoping these 90 users unlock by doing this? We kind of look at authenticating as less of an "admin tells you to do so" thing but rather a "you do this when it makes sense" (aka if you try to take some action to interact, like paste a link, it will ask you to log in)

>It would be better still if the official bot would do a basic unfurl for all channels it was part of if it didn't know who was who. It shouldn't need that information to just display the basics of the ticket?
Unfortunately it does, as we need to verify that the user who shares the link has access to the issue itself. Otherwise, users could unfurl tickets they don't have access to and see information they should not see (like summary, etc.)

The limitation for mapping is for 2 reasons
1. We need to generate user tokens for each user, so that we know who they are in Slack (and map to Atlassian) and can act on their behalf in Slack

2. Slack does not let you, as an admin, generate users on behalf of _other_ users. We're working with Slack on this right now through our partnership, but I would give caution around expecting anything any time soon.

I hope this helps clarify a few things for you
Trevor

Zach Haehn

I have a similar issue - we have several users in our Slack channel that are external guests on our channel. When they try to connect the Jira Cloud plugin, they get a message saying "You're not authorized to install Jira Cloud on <our slack organization name>." How are they supposed to make this happen if they can't authorize themselves? Is this something an admin can do on their behalf?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

integration

slack

administration