You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a WordCamp speaker doesn't have their WordPress.org username added to their Speaker post, the badge automation doesn't run.
When the user comes looking for the badge months later, the date that appears in their profile activity log shows the current time, rather than either a) When the WordCamp was, or b) When the speaker post was published.
This isn't an issue when the badge is added close to the event, but can be 'weird' when we're adding a badge for a WordCamp that happened last year.
To reproduce
Steps to reproduce the behavior:
Edit a WordCamp Speaker profile for a past camp, add the WordPress.org username
View the WordPress.org profile, note that the activity log is today.
Expected behavior
Unsure; This is a situation where I feel that it should have a date in the past, rather than the current timestamp.
Having it in the activity log as Confirmed as a speaker.. today though is weird.
Screenshots / Screencasts
The text was updated successfully, but these errors were encountered:
Describe the bug
When a WordCamp speaker doesn't have their WordPress.org username added to their Speaker post, the badge automation doesn't run.
When the user comes looking for the badge months later, the date that appears in their profile activity log shows the current time, rather than either a) When the WordCamp was, or b) When the speaker post was published.
This isn't an issue when the badge is added close to the event, but can be 'weird' when we're adding a badge for a WordCamp that happened last year.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Unsure; This is a situation where I feel that it should have a date in the past, rather than the current timestamp.
Having it in the activity log as
Confirmed as a speaker..
today though is weird.Screenshots / Screencasts
The text was updated successfully, but these errors were encountered: