diff --git a/.gitlab/issue_templates/deploy-new-stack-in-production.md b/.gitlab/issue_templates/deploy-new-stack-in-production.md
index fde09b1..184f97f 100644
--- a/.gitlab/issue_templates/deploy-new-stack-in-production.md
+++ b/.gitlab/issue_templates/deploy-new-stack-in-production.md
@@ -1,18 +1,20 @@
 /title production: Deploy new <project> stack
 
 /milestone %"Extend archive coverage [Roadmap - Collect]"
 
 /labels ~"activity::Deployment"
 
+*Note* This proposes a plan to deploy the new stack in production. Please,
+drop the unneeded actions from the plan.
 
 - [ ] [swh-charts](https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-charts/-/blob/production/swh/values/production.yaml?ref_type=heads#L126): Checkout production branch
 - [ ] [swh-charts](https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-charts/-/blob/production/swh/values/production.yaml?ref_type=heads#L143): Adapt values to reference the new lister and loader (equivalent to what was done for staging)
 - [ ] Deploy (push branch and let argocd do its job)
 - [ ] Tag grafana with "deployment service=loader-<project> service=<lister-project> environment=production" [1]
 - [ ] Checks pods are doing their jobs
 
 Dashboard to follow [1]
 
 [1] https://grafana.softwareheritage.org/goto/e-c3EAWIz?orgId=1
 
 Refs. <issue>
diff --git a/.gitlab/issue_templates/deploy-new-stack-in-staging.md b/.gitlab/issue_templates/deploy-new-stack-in-staging.md
index abb21e7..e5e1f60 100644
--- a/.gitlab/issue_templates/deploy-new-stack-in-staging.md
+++ b/.gitlab/issue_templates/deploy-new-stack-in-staging.md
@@ -1,19 +1,21 @@
 /title staging: Deploy new <project> stack
 
 /milestone %"Extend archive coverage [Roadmap - Collect]"
 
 /labels ~"activity::Deployment"
 
+*Note* This proposes a plan to deploy the new stack in staging. Please, drop
+the unneeded actions from the plan.
 
 - [ ] [swh-apps](https://gitlab.softwareheritage.org/swh/infra/swh-apps/-/tree/master/apps?ref_type=heads): Build image (if required)
 - [ ] [swh-charts](https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-charts/-/blob/staging/values-swh-application-versions.yaml?ref_type=heads): Reference new image (if required)
 - [ ] [swh-charts](https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-charts/-/blob/staging/swh/values/staging.yaml?ref_type=heads#L126): Adapt values to reference the new lister and loader
 - [ ] Deploy (push branch and let argocd do its job)
 - [ ] Tag grafana with "deployment service=loader-<project> service=<lister-project> environment=staging" [1]
 - [ ] Checks pods are doing their jobs
 
 Dashboard to follow [1]
 
 [1] https://grafana.softwareheritage.org/goto/e-c3EAWIz?orgId=1
 
 Refs. <issue>
diff --git a/.gitlab/issue_templates/deploy-new-stack-version.md b/.gitlab/issue_templates/deploy-new-stack-version.md
index d5474da..46b2670 100644
--- a/.gitlab/issue_templates/deploy-new-stack-version.md
+++ b/.gitlab/issue_templates/deploy-new-stack-version.md
@@ -1,26 +1,28 @@
 /title Deploy new <project> <version>
 
 /milestone %"MRO 2023"
 
 /labels ~"activity::Deployment"
 
+*Note* This proposes a plan to deploy a new version for a given stack (Arch
+Linux, AUR, ...). Please, drop the unneeded actions from the plan.
 
 
 staging:
 - [ ] [swh-apps](https://gitlab.softwareheritage.org/swh/infra/swh-apps/-/tree/master/apps?ref_type=heads): Build image (if required because of new deps for example)
 - [ ] [swh-charts](https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-charts/-/merge_requests): Merge MR with image versions updates triggered by the CI
 - [ ] Push branch 'staging' && Let argocd deploy and do its job
 - [ ] Checks pods are doing their jobs without crashing
 - [ ] Tag grafana with "deployment service=<service> service=<service2> ... environment=staging" [1] [2]
 
 production:
 - [ ] Merge 'staging' branch into 'production' (it should/must be a fast-forward)
 - [ ] Push branch 'production' && Let argocd deploy and do its job
 - [ ] Tag grafana with "deployment service=<service> service=<service2> ... environment=production" [1] [2]
 - [ ] Checks pods are doing their jobs without crashing
 
 [1] https://grafana.softwareheritage.org/goto/e-c3EAWIz?orgId=1
 
 [2] Only reference impacted services (e.g. storage, lister-cran, loader-git, scheduler, vault, ...)
 
 Refs. <issue>
diff --git a/.gitlab/issue_templates/deploy-next-swh-version.md b/.gitlab/issue_templates/deploy-next-swh-version.md
index 360c851..a037942 100644
--- a/.gitlab/issue_templates/deploy-next-swh-version.md
+++ b/.gitlab/issue_templates/deploy-next-swh-version.md
@@ -1,31 +1,33 @@
 /title Deploy next swh version
 
 /milestone %"MRO 2023"
 
 /labels ~"activity::Deployment"
 
+*Note* This proposes a plan to deploy the next swh version. Please, drop the
+unneeded actions from the plan.
 
 Actions:
 - [ ] Tags all impacted modules
 
 Includes:
 - <insert-new-version-packages-with-small-summary>
 - ...
 
 Dependency:
 - <insert-blocking-dependency>
 - ...
 
 staging:
 - [ ] storage1.staging: Upgrade package & Restart gunicorn-swh-storage (if storage is impacted)
 - [ ] <insert-mr-link> swh-charts: Merge new versions
 - [ ] Let argocd deploy
 - [ ] Tag grafana with "deployment service=<service> service=<service2> ... environment=staging" [1] [2]
 - [ ] Checks
 
 production:
 - [ ] saam, moma, webapp1: Upgrade swh.storage package & Restart gunicorn-swh-storage (if storage is impacted)
 - [ ] swh-charts: Merge staging branch into production
 - [ ] Let argocd deploy
 - [ ] Tag grafana with "deployment service=<service> service=<service2> ... environment=production" [1] [2]
 - [ ] Checks