Broadcast Message - Limited CI_JOB_TOKEN removal/change
Before requesting a broadcast message, please be sure to read the latest guidance in the product handbook.
Request for recruiting or otherwise communicating with users via Broadcast Messages
When possible, please create this issue and push it into the approval workflow 30 calendar days prior to your desired "go live" date. This will allow collaborators enough time to support your necessary timing.
Ensuring a positive user experience for our users is the most important factor to consider when deploying messaging in our product. With that goal in mind, we have put in place the following procedures to ensure that in-app messaging does not result in any negative user sentiment.
General in-app messaging guidelines
- Messages must be approved by VP of Product in order to run. If the VPP is not available and the request is time-sensitive, Product Operations
@fseifoddini
can review and approve. - We run a maximum of 2 in-app messages at any given time in order to limit the number of messages a user sees in quick succession.
- Messages run for the shortest amount of time possible.
- Messages are limited to a single page on the site unless there is a business reason to put it on multiple pages.
- Messages should apply to all users that see them.
- When possible, please create this issue and push it into the approval workflow 30 calendar days prior to your desired "go live" date. This will allow collaborators enough time to support you.
If you need to target specific users with your message, or you require action from the user, consider an MR using an alert or banner.
Broadcast Message Capability
- Broadcast Messages are for SaaS.
- You can specify a user role but other user attributes are not available at this time.
- You can select a banner or a notification type.
- You can specify a page/s to display the message on.
Tasks for VP Product
-
Apply label workflow::In review
to this issue -
Review, prioritize and approve this issue by viewing other pending and active broadcast messages on the scheduling board -
Apply a Priority 1
orPriority 2
label, and tag the Requester and comment with any additional feedback or guidance you have
Tasks for Requester
questions below
After you've answered the-
Assign this issue to VP Product @david
for review and approval. Tag the Requester in a comment with a link to #tasks-for-vp-product
After VPP has approved
-
Apply label workflow::In dev
-
Assign to your Stage UX Researcher if you need help with messaging content, target pages, target users, etc -
Once you know the message details, add label workflow::scheduling
and tag the DRIs: Fulfillment PMs@amandarueda
and@doniquesmit
.
Once the message goes live
-
Apply label workflow::production
and leave this issue open while the message is running and live to users -
Set a reminder for yourself to close
this issue on the end date of the broadcast message
Proposed Broadcast Message
Please fill out as much as you can - you can add details later -
Type of message?
- Link (copy & CTA)
What should the message say?
"In GitLab 16.0 (2023-05-22) administrators will need to list which projects can access resources within a project through the GitLab CI/CD Job Token."
HTML
"In GitLab 16.0 (2023-05-22) administrators will need to list which projects can access resources within a project through the <a href="https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html" style="color:blue;">GitLab CI/CD Job Token</a>."
Details
This is pending completion of the new flow to set access for limited CI_JOB_TOKENs that is being scheduled in 15.9 at which point we will publish Deprecation/Removal of the old feature in favor of the new.
Given this is a breaking change we want to give project maintainers as much notice as possible so they can make the change for pipelines using CI_JOB_TOKEN
to keep working.
banner or a notification? (Please note that notifications are limited just one running at a time).
Would you like to run aNotification.
For a banner, what should the background color be?
For a banner, should the message be dismissable?
Which user roles should see this message?
Project Maintainers and Owners.
What pages (target path) should the message be displayed on (Paths can contain wildcards, like */welcome)?
gitlab.com/*/*/-/settings/ci_cd
What is the start date/time in UTC?
2023-02-22 / 16:00 UTC - coincide with 15.9 milestone and availability of the feature replacing this
What is the end date/time in UTC?
2023-05-22 / 16:00 UTC - coincide with 16.0 milestone and removal of the feature.
UX Research project
Is this for user research? (If yes, please link your research issue from theNo