Description: The current projection of a motion with many accepted amendments that are in conflict is not optimal. Many parts are displayed unnecessarily in the projection. In the detailed view of the motion, on the other hand, it is easier to see which parts have been edited and which amendments are in conflict. The projection should use this as a basis.
Example of motion detail view:
Projection of this:
Reproduction:
open a meeting
open motions and create a motion with four paragraphs
create several amendments to the paragraphs with conflicts to each other
Change Status of the amendments to Accepted
Project the Motion in Diff Version
What should happen:
The projection should follow the display in the motion detail view if the checkbox 'Show all changes' is checked. This also makes it easier to see in the projector at which point which change has been made and reduces the display of unnecessary content. (Example: Last three images.)
Important: For a better overview of the necessary adjustments for a motion with many amendments with conflicts, I have split this issue apart from another issue. I think Issue #2936 is pre-required to solve this issue.
MSoeb
commented
2 months ago
Description: The current projection of a motion with many accepted amendments that are in conflict is not optimal. Many parts are displayed unnecessarily in the projection. In the detailed view of the motion, on the other hand, it is easier to see which parts have been edited and which amendments are in conflict. The projection should use this as a basis.
Example of motion detail view:
Projection of this:
Reproduction:
What should happen: The projection should follow the display in the motion detail view if the checkbox 'Show all changes' is checked. This also makes it easier to see in the projector at which point which change has been made and reduces the display of unnecessary content. (Example: Last three images.)
Important: For a better overview of the necessary adjustments for a motion with many amendments with conflicts, I have split this issue apart from another issue. I think Issue #2936 is pre-required to solve this issue.