We have a database for Wiki pages, and a database for Tasks
Both of these are connected to a database with Projects, so that we can easily filter and show tasks/documentation based on a project.
Right now it is possible using the # or the highlight and create entity to create a new database entry. Which is quite ok.
However, this will not automatically link the Project, so a bunch of manual work is still necessary.
Is there a way (or i would like to suggest), some form of automatic linking, so that if both have the same database relation (in this case, both have a Project field), that those would be auto-assigned.
I was thinking of using the References, but I believe the reference is not set on-create, but only after the fact. So that wont work.
In this specific scenario its more that we are making a To Do list for a play session. Or, for example, we are running a test session and write down all the issues we encounter in a wiki page with the testing protocol.
I then immediately translate this To Do list into Tasks, which I would do by highlighting individual items and turning them into task entities (creating the task, and immediately mentioning them in the to do list for our documentation).
However, if I do this, the task will be created without any link to the Project, so they wont appear in my Task Board / Backlog for the Project. Fixing this would require me to click on each individual task, and selecting the Project, which is fine for 2 or 3 tasks, but if the list is longer, then it can be quite the hassle.
Right now the Cardinality for Tasks is one Project to many Tasks, and many Projects to many Wiki Pages. We were thinking of changing that back to a one to many for both Tasks and Wikis for clarity reasons.