Remove invalid data from issue_tracker_data table
What does this MR do?
Rebase of !23759 (merged) for 12-7-stable-ee-patch-5 patch release.
Original description
In !18639 (merged) we started migrating data for issue trackers and jira from `properties` field of `services` table to `jira_tracker_data` and `issue_tracker_data`.We found out that the data were not properly migrated for jira_tracker_data. *_iv values are missing in some cases, mostly for api_url field. This has been fixed in !23621 (merged). We thought (and validated on gitlab.com data) that we don't have the problem for data migrated to issue_tracker_data table.
#198938 (closed), however, reveals that there might be the same problem with issue_tracker_data on customers' instances, too.
The final fix will be reinserting the data correctly but this MR removes the invalid data so that users can use their projects.
The fix is the same as !23621 (merged), we just fix issue_tracker_data instead of jira_tracker_data
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team