Add support for closed event to Vue version of contribution events

Peter Hegmanrequested to merge
378677-add-closed-event into master

What does this MR do and why?

Related to #378677 (closed)

In &9056 we are migrating the user profile from HAML/jQuery to Vue. This is a large migration so we are splitting it up into many sections. This MR continues to build out the Activity section on the Overview tab.

There are many contribution events that we will need to support. These are documented in https://docs.gitlab.com/ee/user/profile/contributions_calendar.html#user-contribution-events. This MR adds the closed contribution event. In future MRs I will be iteratively adding support for the other contribution event types.

UX note: There is currently an incorrect bottom border in the tabs. This is due to a recent change in !118597 (merged). We will be removing the tabs and moving the navigation into the new sidebar in #389842. By removing the tabs we will be able to fix this bug and because this is behind a feature flag I am going to leave it as-is for now.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
127.0.0.1_3000_root (3).png 127.0.0.1_3000_root (2).png

How to set up and validate locally

You don't have to do all of steps 3 - 11 to see events. Those steps are just to help understand which types of resources this MR supports.

  1. Disable the super sidebar if you have it enabled. The Vue profile does not yet support it. Will be supported in #389842
  2. Enable the profile_tabs_vue feature flag
    • bin/rails console
    • Feature.enable(:profile_tabs_vue)
  3. Close an issue
  4. Close a MR
  5. Close an Epic
  6. Close a task
  7. Close a requirement
  8. Close an incident
  9. Close a test case
  10. Close an Objective (see https://docs.gitlab.com/ee/user/okrs.html)
  11. Close a key result (see https://docs.gitlab.com/ee/user/okrs.html)
  12. Visit your profile

MR acceptance checklist

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

Edited by Peter Hegman

Merge request reports