related issues
<ul>
<$list filter="[list[!!title]]">
<li><$view field="title"/></li>
</$list>
</ul>
{{Ticket-001||related}}
filter="[list[!!title]]"
{{Ticket-08 Ticket-15||related}}
2. add this to an issue-tiddler
{{Ticket-001||related}}
This works fine - as long as I also have a tiddler called "Ticket-001". The issue here is this piece of codefilter="[list[!!title]]”
It simply relies on the tiddler to exist. An non-existent tiddler does not have a title field.
So as long as just one ticket is related, I could help myself by simply creating a tiddler for each ticket, which isn't too bad, as I already have that for most of the tickets.
But now the fun part starts.
I want to relate to more than one ticket. So I introduced
{{Ticket-08 Ticket-15||related}}
It took me a while to figure out why this failed, despite the fact, that both Ticket-tiddlers exist.
It's simply that there is no tiddler "Ticket-08 Ticket-15" :(
So what would be YOUR way of solving this conundrum?
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b2665135-b90e-4261-898d-aea7a1e38fa3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I think I’d be inclined to make a global macro:<<related “Ticket-08 Ticket-15”>>
That was my initial idea, but the "problem" here are:
1) The recipients are not really TiddlyWiki users
2) The Data is only intermediate. Eventually the recipients will transfer the data to something else
3) The fields are not automatically searched so they might get problems when trying to find issues
4) The data is not visiple inside the issue tiddlers except if I start to add templates or includes some not-so-obvious macro call in each issue tiddler having related tickets
What recipients? And what are they to receive?
What data, for use where?
It's pretty straight forward to implement a custom search for a tickets field.
That would be the idea, yes... to add conditional ViewTemplates that show stuff conditionally at both issue tiddlers as well as ticket tiddlers... the related lists so to speak.
If you want, I can get you a scaffolding off which to work. Will have to wait until Monday, though.