Default TAG in global config settings #4275

New Issue

OVERLORD · 2026-02-05T08:24:34+03:00

OVERLORD commented

2026-02-05 08:24:34 +03:00

Originally created by @mlipok on GitHub (Oct 20, 2023).

Describe the feature you'd like

I would like to add a default tag for all new BOOKS/CHAPTERS/PAGES, but not for SHELVES.

When creating shelves, we assume that they will contain some content, nad a given book as a document may have an appropriate standardized WIP status. The chapters of a given book and specific pages are also part of the document, but the shelf is not a document.
Therefore, the shelf does not need a default TAG.

For example all new content should be tagged as our tag WIP "work in progress"
This mean that somebody need to review this content.

Describe the benefits this would bring to existing BookStack users

User who creates content will not worry to add this tag.

Moreover, a given organization, in this case mine, has certain rules for creating documentation. In this case, it is necessary to REVIEW new documents and have them approved by the superior.
I think many organizations have such requirements.
The new functionality will significantly help meet these requirements in a way that will ensure repeatability and reduce operational costs.

Can the goal of this request already be achieved via other means?

Yes. You have to remember and fullfil tag.

But the role of the software is not that the user has to remember something, but that the software facilitates and secures the correctness of operations.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

Not using yet, just scoping

Additional context

none

Originally created by @mlipok on GitHub (Oct 20, 2023). ### Describe the feature you'd like I would like to add a default tag for all new BOOKS/CHAPTERS/PAGES, but not for SHELVES. When creating shelves, we assume that they will contain some content, nad a given book as a document may have an appropriate standardized WIP status. The chapters of a given book and specific pages are also part of the document, but the shelf is not a document. Therefore, the shelf does not need a default TAG. For example all new content should be tagged as our tag `WIP` "work in progress" This mean that somebody need to review this content. ### Describe the benefits this would bring to existing BookStack users User who creates content will not worry to add this tag. Moreover, a given organization, in this case mine, has certain rules for creating documentation. In this case, it is necessary to REVIEW new documents and have them approved by the superior. I think many organizations have such requirements. The new functionality will significantly help meet these requirements in a way that will ensure repeatability and reduce operational costs. ### Can the goal of this request already be achieved via other means? Yes. You have to remember and fullfil tag. But the role of the software is not that the user has to remember something, but that the software facilitates and secures the correctness of operations. ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### How long have you been using BookStack? Not using yet, just scoping ### Additional context none

OVERLORD added the 🔨 Feature Request label 2026-02-05 08:24:34 +03:00

OVERLORD commented

2026-02-05 08:24:39 +03:00

@mlipok commented on GitHub (Oct 20, 2023):

Edited few times. sorry. Finall version is above.

@mlipok commented on GitHub (Oct 20, 2023): Edited few times. sorry. Finall version is above.

OVERLORD commented

2026-02-05 08:24:43 +03:00

@ssddanbrown commented on GitHub (Oct 20, 2023):

Thanks for the request @mlipok.

To be honest though, I'm not really keen on adding options/settings like that requested which are primarily to support specific business process.

Ultimately, a specific built-in process like that requested #473 would be more what I'd veer towards as a more substantial targeted of the explained use-case.
Otherwise, the use of templates and the retention of tags, as requested in #1867, might be another angle to this.

If you're confident with PHP, you could alternatively make use of our logical theme system to watch for creation events for certain item types, and apply the desired tags onto them automatically (If not already applied by the user).

There's not an existing hack for this, but this one demonstrates listening for mulitple item-level events and triggering alterations upon them.

@ssddanbrown commented on GitHub (Oct 20, 2023): Thanks for the request @mlipok. To be honest though, I'm not really keen on adding options/settings like that requested which are primarily to support specific business process. Ultimately, a specific built-in process like that requested #473 would be more what I'd veer towards as a more substantial targeted of the explained use-case. Otherwise, the use of templates and the retention of tags, as requested in #1867, might be another angle to this. --- If you're confident with PHP, you could alternatively make use of our [logical theme system](https://github.com/BookStackApp/BookStack/blob/development/dev/docs/logical-theme-system.md) to watch for creation events for certain item types, and apply the desired tags onto them automatically (If not already applied by the user). There's not an existing hack for this, [but this one demonstrates](https://www.bookstackapp.com/hacks/autosort-tagged-books/) listening for mulitple item-level events and triggering alterations upon them.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#4275