Recently, I've noticed a minor issue with the Confluence emails stating, 'Your team is working on these pages.
'The 'Owned by' user information is not displayed correctly; it instead shows 'Owned by First Last.'
I have observed this issue across multiple installations and setups.
Is anyone else experiencing this problem?
Up until the last such email, everything was looking good. This issue probably started with the emails that were triggered today.
I saw this in multiple setups/domains
Yes, perhaps this will be triggered in a new set of emails for this week.
yes, I guess
Yes, I saw this for the first time today as well.
que paso
Hi, @Rishabh Jhawar - I see this, too, but only for my Community Leader Confluence space.
Hi @Amanda Barber ,
I noticed this in the community leader space and also in a work-related space just an hour ago. I suspect that this is a recently introduced bug.
Regards,
Rishabh
Thanks for confirmation @pau
I suspect that it started sometime today.
Hi @Rishabh Jhawar ,
I have created a new page in my personal space yesterday afternoon and 2h later one of my key-users got this email you described.
But we have no clue yet, which behaviour or trigger started this action.
Regards,
Christian
The pages that I got email update for are pretty old (months/years old). I guess this is not for recently created pages but rather issue with how email picks up user names.
Seems like all was ok until yesterday and this issue got introduced yesterday.
I'm seeing this as well.
I'm guessing first and last name is being resolved properly.
Hi, yes, I can confirm this happens in our org emails as well.
Same!
Same with me, I saw the same thing happen to our Confluence emails with yesterday's email as well. :(
Hopefully it is a known bug and in the works for a fix.
@Rishabh Jhawar just jumping in here to let you know I have also been seeing this across all instances since Sunday January 19. I'm hoping an Atlassian Product Team member will jump in here with acknowledgement and an explanation.
I guess this is issue across all instances and hoping the same that someone from Atlassian Product Team to respond.
Received weekly email for this week, I see that issue is now fixed now.
is it fixed for other folks too?
Thanks for sharing your experiences on this thread.
@Andy Gladstone @Miriam Hopton @Annette Herzog-Lang @Richard Ward @Emiliano juan Bradford @Amanda Barber @paul_tansey @Michiel Schuijer