Extend usage data tracking for Slack app GBP migration
Background
We're migrating the Slack app from Classic to GBP, and will probably deprecate the Classic app / supporting code at some point: &7729 (closed)
We want to track the rollout of the updated GBP app, and see how many are still using the Classic app so we can decide when to remove any legacy code.
Proposal
We could store the "version" (Classic/GBP) in the DB similar to how we do this with Jira (Cloud/Server). Based on the number of GBP installs we can deduce the number of Classic installs (which have already happened in the past, so we don't get a chance to store the version for them).
It probably makes sense to store this in the SlackIntegration
record, which is different from Integrations::GitlabSlackApplication
and more like JiraConnectInstallation
Availability & Testing
Suggestion:
- add unit tests around the usage data counting
-
package-and-qa
on the MR.