Skip to content

Consistently use `mmm dd, yyyy` format for analytics dates

Alex Pennells requested to merge 420815-consistent-date-format into master

What does this MR do and why?

Consistently use mmm dd, yyyy format for analytics dates. Converts Value stream, contributor and CI/CD analytics.

Areas that have been updated:

Areas that have not been updated:

  • Pipelines chart was not updated in this MR as the date ranges are generated on the backend. This was separated into a separate issue (#432822)

Screenshots or screen recordings

Before After
Screenshot_2023-11-23_at_11.14.17_AM Screenshot_2023-11-23_at_11.08.45_AM
Screenshot_2023-11-23_at_11.14.48_AM Screenshot_2023-11-23_at_11.09.00_AM
Screenshot_2023-11-23_at_11.15.05_AM Screenshot_2023-11-23_at_11.09.27_AM
Screenshot_2023-11-23_at_11.15.21_AM Screenshot_2023-12-01_at_3.48.53_PM
Screenshot_2023-11-23_at_11.15.34_AM Screenshot_2023-12-01_at_3.49.07_PM

How to set up and validate locally

  • Create test project:
    • FILTER=customizable_cycle_analytics SEED_CUSTOMIZABLE_CYCLE_ANALYTICS=1 bundle exec rake db:seed_fu
  • Navigate to the newly created project
  • Analyze > Value stream analytics
    • Overview tab: Verify date on X axis and in tooltip
    • Any other tab: Verify date on X axis and in tooltip
  • Analyze > Contributor statistics
    • Top graph: Verify date in tooltip
    • User graphs: Verify date in tooltip
  • Analyze > CI/CD analytics
    • Pipelines tab: Verify date range above the chart
    • Any other tab: Verify date range above the chart, and the date on the X axis and in tooltip

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #420815 (closed)

Edited by Alex Pennells

Merge request reports