Skip to content

Determine team names and labels

We will split our team around the Day 1/Day 2 theme to build specialty around customer experience of Distribution. In the vein of this context, we need to give two teams new names and create associated labels for labeling the backlog.

Defining the two focus themes

Some ideas but not limited to

  1. Distribution:Day 1, Distribution:Day 2
  2. Distribution:Greenfield, Distribution:Upgrade

Other suggestions are welcome.

Some factors to consider

  1. Aligned to our vision of Day 1/Day 2 customer experience theme
  2. Crisp and easy for external groups to determine DRI

Auto-Summary 🤖

Discoto Usage

Points

Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive) point:. For example, the following are all valid points:

  • #### POINT: This is a point
  • * point: This is a point
  • + Point: This is a point
  • - pOINT: This is a point
  • point: This is a **point**

Note that any markdown used in the point text will also be propagated into the topic summaries.

Topics

Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.

Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive) topic:. For example, the following are all valid topics:

  • # Topic: Inline discussion topic 1
  • ## TOPIC: **{+A Green, bolded topic+}**
  • ### tOpIc: Another topic

Quick Actions

Action Description
/discuss sub-topic TITLE Create an issue for a sub-topic. Does not work in epics
/discuss link ISSUABLE-LINK Link an issuable as a child of this discussion

Last updated by this job

Discoto Settings 
---
summary:
  max_items: -1
  sort_by: created
  sort_direction: ascending

See the settings schema for details.

Edited by Jason Plum