Feature: Naming Template System for Cards, Content, Attachments

[DrDBanner]

Referring back to issue #7396

When cloning a card while preserving attachments, there is an immediate side effect:

All attachments are stored directly inside the Deck folder of the Nextcloud client. So if two attachments have the same filename, the client creates duplicates like “file.md” and “file (1).md”. Technically this works, but it quickly leads to messy and inconsistent filenames.

What I’d really like is an option for consistent, rule-based naming for Deck as a whole. Ideally, Deck would support a global naming pattern such as:

{Title:key}-{Customer:key}-{CustomerNumber:key}-{Whatever:key}

This could then be applied throughout the entire workflow.

Imagine a card that follows a structured workflow with:

• a description
• links to files
• links to global data
• recurring attachment files like note.md, planning.md, do-this.md

Now the card’s title might follow something like {Title}-{Customer}-{SubContext}, and inside the card body you might have other {Context:key} pairs. Anything, including attached files could be named like {SubContext}-{Customer}-whatever-string | .xlsx | .md | .doc ....

If cloning automatically updates all {key:value} pairs, after the context has been applied by an optionally manual step in between, everything stays clean and consistent.

This would be extremely useful.

However, it’s also a fairly big feature.

It would require:

• A mapper
• A mapper interface for user-defined settings
• Some process for managing context during creation/cloning so that cards can inherit or override key–value pairs

---

Note to myself:

And when thinking this through, this could even grow into a system-wide solution for all Nextcloud apps: a general key:value:context mapping framework that allows highly individual naming schemes and relationships between objects.

Basically, this could serve as the foundation for the bigger idea described here:
nextcloud/server#53125

---

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.