Update sharding_key_issue_url for some integration tables

George Koltsovrequested to merge
georgekoltsov/update-sharding-key-yml-files-for-integrations into master

What does this MR do and why?

This MR updates sharding_key_issue_url for 4 integrations related tables:

  • jira_tracker_data
  • issue_tracker_data
  • zentao_tracker_data
  • slack_api_scopes

Main reason: as per discussion in #463856 (comment 2570349452) each table should have a separate issue url, while at the moment all 4 tables point to the same issue. This MR sets each table to a separate issue.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports