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
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
Firestorm user, Jules Catlyn, reported group notice timestamps all showing same date and time.
After investigation, it was discovered this only occurred on Server Channel 540369.
It does not occur on Server Channels 540037 or 540213.
What were you doing when it happened?
Checking group notice timestamps.
What were you expecting to happen instead?
Timestamps to be reflected accurately.
Other information
Thanks go to Jules Catlyn for bringing this to our attention.
Group Notice Timestamps don't report accurately Server Channel 540369/ now 541440
Type
Bug
Priority
Unset
Status
Closed
Resolution
Accepted
Reporter
Willow Wilder (willow.wilder)
Created at
2020-04-22T16:17:47Z
Updated at
2021-02-01T18:09:14Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
"Is there anything you'd like to add?": 'Thanks go to Jules Catlyn for bringing this to our attention. ',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'Firestorm user, Jules Catlyn, reported group notice timestamps all showing same date and time. \r\nAfter investigation, it was discovered this only occurred on Server Channel 540369. \r\nIt does not occur on Server Channels 540037, 540213, or 540213. ',
'What were you doing when it happened?': 'Checking group notice timestamps.',
'What were you expecting to happen instead?': 'Timestamps to be reflected accurately. ',
'Where': 'http://maps.secondlife.com/secondlife/Magnum%20Sandbox%20A/47/46/34',
}
The text was updated successfully, but these errors were encountered:
What just happened?
Firestorm user, Jules Catlyn, reported group notice timestamps all showing same date and time.
After investigation, it was discovered this only occurred on Server Channel 540369.
It does not occur on Server Channels 540037 or 540213.
What were you doing when it happened?
Checking group notice timestamps.
What were you expecting to happen instead?
Timestamps to be reflected accurately.
Other information
Thanks go to Jules Catlyn for bringing this to our attention.
Attachments
Links
Duplicates
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: