Improve explanation of on-call participants creation
What does this MR do?
Addresses a minor fix for #323875 (comment 525195923).
The color corresponding to a participant's shifts in an on-call schedule is saved with the participant and can be set via the API. The frontend sets these values when saving a new on-call schedule.
The expected colors for the frontend are https://design.gitlab.com/data-visualization/color/#categorical-data, but the backend accepts more weights than the frontend can render. If an improper weight is used in the API, it will show up as white in the UI.
This is an edge case for sure, so we're limiting the solution to documenting the caveat for the graphql endpoint for the time being, as this really isn't a priority. The feature is still behind a feature flag.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. - [-] I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
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