Tag inheritance

Hello,

This was requested in the past in the following thread, so we will note your interest for this feature.

Regards,

Hi,
any news regarding this feature request? We would really appreciate this functionality.
Thanks.

BR,
Martin

Hello Martin,

Nothing new for now but I encourage you to upvote the thread so we can more easily see user interest for this feature.

Regards,

Hello @timhauptmann and @martindvorsky ,

We're currently working on implementing a configuration to allow inherited tags. I had one question for you regarding this part:

with the option to deactivate this per entry

At the moment in our internal development, we can configure this in the vault or the system settings, so that administrators can have this apply to specific vaults, or to their whole system more easily. We didn't want to complexify configurations more, so we were opting to not have it be configurable in entries (folders or sessions) directly.
Is being able to deactivate this per-entry something crucial for the environment you're trying to configure? If it is, we will have to adjust our solution.

Regards,

Hi Hubert,
in my case it would be a nice-to-have feature, but it isn't a show stopper. We can make a workaround, for example create a separate entry (not subentry) when we don't want to inherit tags.

BR,
Martin

Hello,

Thank you for the feedback.

We can make a workaround, for example create a separate entry (not subentry) when we don't want to inherit tags

That's correct, this would work as long as the entry isn't in a folder where the folder or its parent folders contain tags. If they do, then this entry would also have the tags belonging to these folders.

For now, we will stick to having it be configurable at the vault and system setting levels. As usual, we are open to feedback, and if we (or our users) realise that having this granularity would be beneficial despite complexifying the configuration, then we will add it.

Regards,