Mission Prio – Documentation Guidelines

Purpose

The Mission Prio functionality is designed to help development teams work in a structured and prioritized way by grouping issues into “missions” and guiding the team through them in a logical, top-down order. This document outlines how to correctly configure missions using GitLab Wikis. And how the Mission Prio bot selects issues for execution.

Creating a Mission Roadmap Wiki Page

To enable the Mission Prio bot to work correctly, a roadmap wiki page needs to exist first:

1. Wiki Page Naming

   • The title of your Wiki page must include the word roadmap. Otherwise the bot can not find the missions.
   • The roadmap wiki pages may exist on project and group level, the bot will scan for new wiki pages periodically.
   • In the roadmap wiki page, note the mission labels, for example: ~“mission:MoreSignups ”. You can add multiple missions in one wiki page.

2. Mission Order

   • Define missions in top-to-bottom order on the page.
   • The mission listed at the top is the mission that needs to be completed first.

3. Mission Labeling

   • Each mission must have a label in the following format:

     mission::mission_name

     Place this label next to the mission name in the Wiki page. Make sure you make this label on the group level in Gitlab if the mission stretches over multiple projects. The reason for the format can be found in Gitlab page.

   • Example:

     - Q1-2025-bot-deployment ~"mission:bot-deployment"
     - Q2-2025-bot-finetuning ~"mission:bot-finetuning"

   Make sure when adding the label in the wiki you use the markdown style of Gitlab to display labels.

   • Assign the corresponding mission label to all issues that belong to that mission.