Bug: POST /projects/{id}/lifecycleevent takes wrong payload. Issues with logic are also possible.

Description

Look at the below Swagger. The provided example payload is wrong.

Check with the CollaborationProject, AbstractCollectionLifecycleEvent, CollaborationProjectDataCollection schemas

image

Acceptance criteria

[What needs to be done for the story to be complete?]

Testing scenarios

[What testing should be done to make sure the output works as expected?]

Technical notes

[Any technical details, guides, documentation, wikis, and many more that could be useful to complete this story.]


  1. Validate payload fields againts AbstractCollaborationLifecycleEvent.1.0.0
  2. Payload should not include EventId - generated and check unique
  3. Datetime should not be included in request - generated
  4. Apply ResourceIDs array / WIPResourceIDs and create Storage record ResourceCollectionID / WIP ResourceCollectionIds under the hood
  5. Create ENUM for reserved names (OPEN, CREATED, CLOSED, RESOURCES_ADDED, RESOURCES_DELETED, WIP_RESOURCES_ADDED, WIP_RESOURCES_DELETED, PUBLISH - Human readable Camel case), and support custom input
Edited Jul 02, 2024 by Dmitrii Novikov (EPAM)
Assignee Loading
Time tracking Loading