Sync update of title and description between RequirementsManagment::Requirement objects and requirement type issues
What does this MR do?
Now that !64291 (merged) is merged, we can move to syncing the updating of either requirement issues or their associated Requirements.
Part Stage IIb in #323779 (closed).
Syncs updates of Title and Description of Requirements and their associated requirement-type Issues. This happens regardless of the associated issue type of a Requirement.
There are several ways a requirement can be updated that should be reflected in the requirement-type issue to which it's associated:
- Toggled archived (closed) or open
- Title changed
- Description changed
- Project changed (read: moved) -> will be prohibited
This MR handles just handles sync of title and description. See #323779 (closed) for completion and context details.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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
Related to #323779 (closed) and #337190 (closed)