Move and aggregate topics into another viewpoints

[DariaSegalard]

Description

What is the valuable outcome that cannot be achieved with current features?

For the moment, users can only reorganize topics within a viewpoint. Stakeholders would like to have the opportunity to act on the viewpoints' global architecture, for example to put 3 different viewpoints' topics in a common one, to move a topic to another existing viewpoint, etc.

For which stakeholder (people, role, project, domain) is it important?

Especially for people who want to reorganize the existing viewpoints, aggregate them or refactor some of their topics.

Which user action should be enabled (or restricted)? For who?

Examples: Aggregating 3 viewpoints to a common one :

• Allow the viewpoint's creator or one of its contributors to move all the topics to another viewpoint (existing or not).
• The user should have the rights to edit this other viewpoint.

Additional details (solutions you think about, or workarounds you tried)

Deliverables status

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

Phase 3

• Screencast