Skip to content

Prevent updating requirement deprecated attributes

Felipe Cardozo requested to merge issue_361990-prevent_updating_requirement_deprecated_fields into master

What does this MR do and why?

Requirements objects are deprecated in favor of work items(issues), They are used only as a proxy to keep iid consistency and API endpoints compatible.

On the database requirements table, we only need to keep some columns:

  • project_id
  • issue_id
  • iid

These columns should not be updated at all and because all others are going to be ignored on #358976 (closed) we can deprecate RequirementsManagement::UpdateRequirementService and cleanup code that we used before to keep requirements and issues in sync.

To properly perform this cleanup we need to start using IssuesUpdateService on our current GraphQL requirements update endpoint and allow the service to update requirement verification status, we need this because the endpoint is still used by UI, but it should be deprecated in the next major version.

related to #361990 (closed)

How to set up and validate locally

  1. Create a requirement
  2. Update the requirement verification status using the UI
  3. Check if everything is worked as it should

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 Felipe Cardozo

Merge request reports