Add owners fields to project webhook data
What does this MR do and why?
We're moving towards Owner role being possible in Projects. Because multiple owners will be possible soon, we are phasing out owner
.
This replaces project.owner
with an equivalent deprecated method in webhook data. It also adds owners
so we can deprecate the owner
field for consumers who might be still using it.
This should NOT introduce a change in the behaviour for owner_name
and owner_email
. To proceed with the goal of phasing out owner
and also minimising customer impact, I suggest the following:
- add another field
owners
which returns the information for all of the Project's direct owners (the personal project's user, or in the case of a Group project, the Group's direct owners) - deprecate the
owner_name
andowner_email
- remove the deprecated fields by %15.0
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #350603 (closed)