aboutsummaryrefslogtreecommitdiff
path: root/doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn
diff options
context:
space:
mode:
authorSimon McVittie <smcv@ http://smcv.pseudorandom.co.uk/>2008-07-21 12:47:07 +0100
committerSimon McVittie <smcv@ http://smcv.pseudorandom.co.uk/>2008-07-21 12:47:07 +0100
commite3a84952715cdd625258e1695cb74898006c31f3 (patch)
tree1a89a49e337991a46a61e66a5779df6a414c35a1 /doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn
parent404f54ac60eac6c7ab93cc47a466d7e0fae35821 (diff)
downloadikiwiki-e3a84952715cdd625258e1695cb74898006c31f3.tar
ikiwiki-e3a84952715cdd625258e1695cb74898006c31f3.tar.gz
Migrate escaped directives (\[[) in the rest of doc to have \[[! prefix
Diffstat (limited to 'doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn')
-rw-r--r--doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn b/doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn
index 665c695d2..ea7835b33 100644
--- a/doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn
+++ b/doc/tips/integrated_issue_tracking_with_ikiwiki.mdwn
@@ -137,7 +137,7 @@ etc, to document different stages of
their lifecycle. A developer can take ownership of a
bug by tagging it with something like "owner/Joey".
-To tag a wiki page, edit it and add text such as "\[[tag done]]". Note that
+To tag a wiki page, edit it and add text such as "\[[!tag done]]". Note that
adding a wiki link to "\[[done]]" will have the same categorisation effect
as a tag, but the link will show up in the body of the page, which is a
nice effect if used in a sentence such as "This was \[[done]] in version
@@ -155,23 +155,23 @@ be inlined into a given page. A few examples:
* A typical list of all open bugs, with their full text, and a form to post new
bugs.
- \[[inline pages="bugs/* and !link(done) and !*/Discussion" actions=yes postform=yes show=0]]
+ \[[!inline pages="bugs/* and !link(done) and !*/Discussion" actions=yes postform=yes show=0]]
* Index of the 30 most recently fixed bugs.
- \[[inline pages="bugs/* and link(done) and !*/Discussion" sort=mtime show=30 archive=yes]]
+ \[[!inline pages="bugs/* and link(done) and !*/Discussion" sort=mtime show=30 archive=yes]]
* Index of the 10 most recently active bugs.
- \[[inline pages="bugs/* and !link(done) and !*/Discussion" sort=mtime show=10]]
+ \[[!inline pages="bugs/* and !link(done) and !*/Discussion" sort=mtime show=10]]
* Open security issues.
- \[[inline pages="bugs/* and link(security) and !link(done) and !*/Discussion"]]
+ \[[!inline pages="bugs/* and link(security) and !link(done) and !*/Discussion"]]
* Full text of bugs assigned to Joey.
- \[[inline pages="bugs/* and link(owner/Joey) and !link(done) and !*/Discussion" show=0]]
+ \[[!inline pages="bugs/* and link(owner/Joey) and !link(done) and !*/Discussion" show=0]]
It may seem strange to consider using a wiki for issue tracking when there
are several dedicated bug tracking systems, like Bugzilla, that handle all