OpenSlides / OpenSlides/openslides-client

Consultation sequence: Motion forwarding more detail

Open
#6,442 6 comments 0 reactions 1 assignee View on GitHub

@Elblinator is already working on this.

Since Aug 13, 2026.

feature Lorentz
Dominant language
TypeScript
Stars
35
Forks
52
Avg merge
1d 9h
Merged PRs (30d)
52

Description

Current behavior
Currently it is only possible to see a limited path of motion forwarding. It is not possible to see the whole path. It is restricted. This limits the usefullness of the motion forwarding.

Wanted behavior

  • A motion session sequence should be integrated into the motion detail view, which displays all forwarding steps of a motion in the order they occurred as a simple path model. This enables the traceability and tracking of motions.
  • Each forwarding step is displayed with the meeting title and current motion state.
    • The visibilty of the state should limited by the workflow restriction of the meeting of the motion. (Example: If there is a restriction set to the motion submitter, the motion sequence should not display it.)
  • In addition, motion metadata (location and date) is visible via tooltips .
  • If accounts have access to a meeting, the meeting titles can be used as links to the meeting; excactly to the motion.
  • If a motion in the path is in a closed meeting,
    • the path should show this meeting as '[Lock-Icon] Closed Meeting Meeting title' without a tooltip.
    • If a user has access to the closed meeting, the name of the meeting with tooltip should be shown.
  • [optional/will follow later] This feature can be enabled via a motion setting. The setting should be added in the meeting settings > motion > Forwarding > activate session sequence. The setting should be activated by default.

See the mockup for details.

Image Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.