Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>
Clone
HTTPS:
git clone https://vervis.peers.community/repos/yEzqv
SSH:
git clone USERNAME@vervis.peers.community:yEzqv
Branches
Tags
ticket-bucket-list.mdwn
[[!inline pages=""“ pages=”"“/* and !/discussion and !// pages=”""* and !/discussion and ( ) and tagged(tickets/class/) and (!* or !tagged(tickets/done) or tagged(tickets/done) )""" archive=yes show=0 rootpage=“” postformtext=“Add a new ticket titled:” ]]
This template summarizes the tickets of a bucket into a single page. It also generates feeds you can subscribe to, e.g. to keep an eye on the bugs of a specific project. Parameters:
pages: [[ikiwiki/PageSpec]] of the pages in the bucket. Use this ifrootpagedoesn’t work for your bucket, i.e. the bucket directory setup is unusual.rootpagestill must be specified if you want to generate the post form.rootpage: The root page of the bucket, if one exists. Usually, the bucket is all the pages right under the root, excluding some special pages or patterns, such as the Discussion page. If you userootpage, the template will take care of the exceptions for you. Ifpagesif specified, it will be used instead to define the bucket.rootpagealso sets the page under which new pages will be created by the post form.post: Whether to generate a post form in the web UI where you can enter a ticket title and click on a button to create it. If specified,rootpagemust be specified too, to choose under which page these new tickets will be created. (default: no)classes: PageSpec of the ticket classes to include, usingtagged(). The spec must be of the formtagged(tickets/class/C1) and ... and tagged(tickets/class/Cn). Having a single class works too, and then noandis needed. (default: all)open: Whether to include open tickets (default: no)closed: Whether to include closed tickets (default: no)
If neither pages nor rootpage are supplied, all tickets pages from the entire wiki are collected.
At least one of open and closed must be supplied.