Improve consistency of how AI feature availability is announced in product
Description
As new AI features are created we have seen several different ways that they've been announced (or not) to users. We'd like to define a method that should be used across all AI feature releases. We'll need to determine what stage these announcements should be made at:
- Experiments
- Beta
- GA
Can be promoted in the user interface through discovery moments, if needed. — https://docs.gitlab.com/ee/policy/alpha-beta-support.html
https://design.gitlab.com/usability/feature-management#discovery-moments
Checklist
Make sure the following are completed before closing the issue:
-
Assign the correct component label to this issue. -
Create an MR with the additions or updates needed. -
When applicable, create an issue using the Figma update
issue template to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling. -
When applicable, create an MR in GitLab UI to update the component. If you do not have capacity or are unable to update the component directly, create a GitLab UI issue using the Component
issue template. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting. -
🎉 Congrats, you made it! You can now close this issue.
Edited by Pedro Moreira da Silva