MySQL Bugs: #30805: Inconsistent expiration display and calculation

Bug #30805	Inconsistent expiration display and calculation
Submitted:	4 Sep 2007 19:23	Modified:	10 Sep 2007 18:56
Reporter:	Joshua Ganderson	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Enterprise Monitor: Server	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
The current implementation of expiration at server level and UI level have some consistency issues.

How to repeat:
See expiration dates in the UI as users in different timezones. Compare to what you would expect expiration to be given date string in contract.

Suggested fix:
 * Make the date string from contract be processed as being in the server's timezone.
* Make expiration display in the UI display hour and minute granularity so that it can indicate an expiration in the middle of the day.
* Calculate days remaining or lapsed as calendar days for the logged in user.
* If hours remaining or lapsed is less than 24, show hours instead of days.
* Provide explanations where necessary that expiration is relative to server time rather than user time.

Note: revisit proposal with mtx gang before implementing.

Documented as a known issue.

This bug is not scheduled to be fixed at this time.