Rethink current iteration filtering and scoping idea in context of multiple cadences.

Context

With introduction of multiple iteration cadences the current iteration meaning shifts to a specific cadence, so does the meaning of current iteration within:

• issue lists
• issue boards

Problems

• How do we handle issue lists filtered by current iteration?
  • 
• How do we handle boards scoped to current iteration?
  • 

Options

• How do we handle issue lists filtered by current iteration?
  • TBD
• How do we handle boards scoped to current iteration?
  • For current boards, we can write a migration for boards that are currently scoped to current iteration to scope those to its corresponding iteration cadence. IMPORTANT: this needs to happen before we can release multiple iteration cadences, i.e. iteration cadences CRUD operations.
    • this is probably already broken as we released overlapping dates validation within groups. So perhaps users will need to configure their boards to scope them first by the cadence and afterwards by the current iteration.
  • Further on when scoping a board to "CURRENT" iteration, we need to get the information from the user which cadence is being referred if there are multiple cadences.

This does require a UX/UI solution as well.

This is a blocker for unveiling iteration cadences, as once users start creating multiple iteration cadences we will no longer be able to scope a board to current iteration.

Proposal

• #323653 (closed)

Auto-Summary 🤖

Solution

Users have the ability to scope a board to a specific iteration or all open iterations within a cadence.

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

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.