Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set all pages to draft when duplicating region #1517

Closed
timobrembeck opened this issue Jun 1, 2022 · 2 comments · Fixed by #1546
Closed

Set all pages to draft when duplicating region #1517

timobrembeck opened this issue Jun 1, 2022 · 2 comments · Fixed by #1546
Assignees
Labels
‼️ prio: high Needs to be resolved ASAP. 💡 feature New feature or request ☺️ effort: low Should be doable in <4h
Milestone

Comments

@timobrembeck
Copy link
Member

timobrembeck commented Jun 1, 2022

Motivation

When a region is cloned, the content needs to be reviewed before it is usable

Proposed Solution

When a region is cloned, all pages of the new region should be set to draft.

Alternatives

Additional Context

@timobrembeck timobrembeck added 💡 feature New feature or request ⁉️ prio: low Not urgent, can be resolved in the distant future. ☺️ effort: low Should be doable in <4h labels Jun 1, 2022
@timobrembeck timobrembeck added this to the Backlog milestone Jun 1, 2022
@dkehne
Copy link

dkehne commented Jun 13, 2022

@timoludwig we have discussed internally and we do not need the bulk action BUT we would like to have the behaviour that after a duplication (of an instance) all pages are on "draft"-status.

@dkehne
Copy link

dkehne commented Jun 13, 2022

prio medium-high if not much effort.

@timobrembeck timobrembeck changed the title Add bulk actions for publishing/saving as draft Set all pages to draft when duplicating region Jun 14, 2022
@timobrembeck timobrembeck self-assigned this Jun 14, 2022
@timobrembeck timobrembeck modified the milestones: Backlog, 22Q2 Jun 14, 2022
@timobrembeck timobrembeck added ‼️ prio: high Needs to be resolved ASAP. and removed ⁉️ prio: low Not urgent, can be resolved in the distant future. labels Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
‼️ prio: high Needs to be resolved ASAP. 💡 feature New feature or request ☺️ effort: low Should be doable in <4h
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants