Since a couple of days ago we have stopped getting the NAMES of those who perform an activity (such as transitioning/assigning/etc) in our Slack integration channel, and it's very annoying:
Jira Cloud APP [10:05 AM]
*transitioned* a bug from `Tasks` ⟶ `In Progress`
*DT-2952 Undefined offset/index*
Jira Cloud APP [10:12 AM]
*assigned* a bug from *Unassigned* ⟶ *Влад Третяк*
*DT-2953 Check user in the operator*
Jira Cloud APP [10:22 AM]
*transitioned* a bug from `Tasks` ⟶ `In Progress`
*DT-2953 Check user in the operator*
The only places where we still see names in Slack are when CREATING tasks:
Jira Cloud APP [9:55 AM]
Rana Khoury has created a *Bug*
*DT-2953 Check users in the operator*
Can anyone suggest what could be the problem?
Hey @Ofer Shapira and @Derrick Moyer ,
Sorry about the trouble you saw with notifications! We've fixed this issue and notifications into Slack should be back to normal and showing users again.
Cheers,
Daniel | Atlassian Support
Thank you for following up!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Daniel Eads, the JIRA Cloud Slack bot is still returning `@undefined` instead of the actual usernames inside the quote section for us. This is after removing the Slack subscription and adding it again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Daniel Eads , we are also facing the same issue. All the username mention is showed as @undefined in the quoted message. May I know if there is any fix for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Btw this issue only happen to us when we use '@' in comments. It is working fine for '@' used in ticket description.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anthony Madhvani and @Stephen Li Yilin - thanks for noting the behavior you saw! In certain situations the integration was having trouble fetching the right name to display. We've pushed out a change that will use an @mention name now if it isn't able to get the full name for some reason. Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Noticing this same issue on my end. @Ofer Shapira have you by chance transitioned to the new view for issues in Jira? We have and I wonder if this is related. Regardless, would love a solution!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe, the reason is a new Atlassian privet policy by GDPR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.