Something odd happened three hour ago. I was notified that in our cloud instance many users appear to have created a new Profile page in their Confluence personal space - and they haven't, users affected by this told me.
My Confluence user is affected as well. So my username "craddatz" shows fine as the title in the Atlassian People profile page. The URL for that page sits on our company.atlassian.net domain and shows /people/prefix:a-very-long-hexadecimal-id.
When I click on my personal space link from the avatar page lower left, I get to see the last changes I authored - which now includes a profile page listed as "User: al-id", where the "al-id" is hex and taken from the URL bit above, crated three hours ago. I did not create that page.
The corresponding page has that "User: al-id" as its title and shows:
Recently Updated
- User 8ab44 about 3 hours ago • created by Carsten Raddatz
None of our users re-created their own user profile page.
So the page itself appears to function as an alias for e.g. https://company.atlassian.net/wiki/spaces/~craddatz/overview and the content shows fine, and the URI part with my name shows just fine.
The title of that page though contains "User al-id". Editing it gets me to People / User al-id / Pages / Carsten Raddatz’s Home and I can't edit my own page's title.
None of us created their own page manually, and very likely nobody triggered a creation of that via JQL. A quick count reveals that some 19 users are affected, and we have no clue why all of this happened.
While this is far from tragic, quite a few people here were confused. Hope that the observed systematic behaviour, while erratic, helps to pinpoint what has been going on.
Any pointers?
Edit: some clarifications and JQL- and GDPR-related links - we found that there were GDPR-related changes and automated conversions that Atlassian did in the background: https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud and https://developer.atlassian.com/cloud/confluence/context-parameters/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.