Hey!
One feature that I have NO idea how one would go and implement would be to somehow populate the dropdown fields dynamically. For example my Task template looks like this atm:
### TODO <%setinput: title%>
type:: [[Task]]
area:: <%setinput: area:[[One-of-my-areas]], [[Another-area]] %>
project:: <%setinput: project: , [[One-of-my-projects]], [[Another-project]] %>
people:: <%setinput: people%>
tags:: <%setinput: tags%>
ticket:: <%setinput: ticket%>
git:: <%setinput: git%>
wiki:: <%setinput: wiki%>
url:: <%setinput: url%>
It would be awesome to have the area and project somehow populated by a Logseq query or something.
But to be quite frank I would be totally fine with only #23 implemented in all of the fields instead. I wouldn't need it to actually be a dropdown, just an easier way to go selecting a project without accidentally mistyping it.
Hey!
One feature that I have NO idea how one would go and implement would be to somehow populate the dropdown fields dynamically. For example my
Task templatelooks like this atm:It would be awesome to have the area and project somehow populated by a Logseq query or something.
But to be quite frank I would be totally fine with only #23 implemented in all of the fields instead. I wouldn't need it to actually be a dropdown, just an easier way to go selecting a project without accidentally mistyping it.