Wiki Lists en » 履歴 » リビジョン 9
リビジョン 8 (Tomohisa Kusukawa, 2015/07/19 23:50) → リビジョン 9/16 (Tomohisa Kusukawa, 2015/07/27 08:22)
h1. Redmine Plugin: Wiki Lists {{count}}
{{>toc}}
日本語は [[Wiki Lists|こちら]].
This plugin adds wiki macros that display ticket lists.
h2. Links Downloads
redmine.org: http://www.redmine.org/plugins/redmine_wiki_lists
repository: https://bitbucket.org/tkusukawa/redmine_wiki_lists
downloads: bitbucket: https://bitbucket.org/tkusukawa/redmine_wiki_lists/downloads
h2. Installation
# Download zip file from "bitbucket":https://bitbucket.org/tkusukawa/redmine_wiki_lists/downloads
# Unzip
# Move the unziped folder into the $REDMINE/plugins/
# Restart REDMINE
h1. Usage
h2. ref_issues
ref_issues macro displays list of issues.
h3. Syntax
{{@ref_issues([option].., {{@ref_issues([options].., [column]..)@}}
*options:*
superseded {{collapse
|* -s[=WORD[｜WORD]..] * -s[=WORD[|WORD]..]
select issues that contain WORDs in subject.
* -d[=WORD[｜WORD]..] -d[=WORD[|WORD]..]
select issues that contain WORDs in description.
* -w[=WORD[｜WORD]..] -w[=WORD[|WORD]..]
select issues that contain WORDs in subject or description.
* -p[=IDENTIFIRE]
Specify the project by identifire.|
}} identifire.
* -i=CUSTOM_QUERY_ID
Use custom query by id.
* -q=CUSTOM_QUERY_NAME
Use custom query by query name.
* -f:ATTRIBUTE OPERATOR [VALUE[|VALUE...]] -f:ATTRIBUTE[=WORD[|WORD...]]
Additional filter. Attributes are shown below.
[ATTRIBUTE]
<pre>
tracker_id,project_id,subject,description, |tracker_id,project_id,subject,description,
due_date,category_id,status_id,assigned_to_id,priority_id,
fixed_version_id,author_id,lock_version,created_on,updated_on,
start_date,done_ratio,estimated_hours,parent_id,root_id,
lft,rgt,is_private,closed_on, cf_*
</pre>
[OPERATOR]
<pre>
=:is, !:is not, o:open, c:closed, !*:none,
*:any, >=:>=, <=:<=, ><:between, >t+:in more than,
>w:this week, lw:last week, l2w:last 2 weeks, m:this month, lm:last month,
y:this year, >t-:less than days ago, ~:contains, !~:doesn't contain,
=p:any issues in project, =!p:any issues not in project, !p:no issues in project,
</pre> cf_*|
You can specify two or more select option, it affect AND condition.
WORDs is one or more search words divided by '|', and multiple words affect OR condition.
If you use this macro in a Issue, you can use the field value specify no select condition, page name of the issue as VALUE by writing to the following field(column) name in the [] (brackets).
* -l[=column]
Put linked text.
* -t[=column]
Put markup text.
* -c
wiki or number of issues. issue is used for search word.
*columns:*
You can choose columns that you want to display.
If you do not specify the columns, same columns with customquery are displayed.
* project
* tracker
* parent
* status
* priority
* subject
* author
* assigned_to
* updated_on
* category
* fixed_version
* start_date
* due_date
* estimated_hours
* done_ratio
* created_on
* closed_on
* relations
h3. example
|\2. *1. use custom query by ID*|
|notation|{{@ref_issues(-i=9)@}}|
|results|{{ref_issues(-i=9)}}|
|\2. *2. use custom query by name*|
|notation|{{@ref_issues(-q=MyCustomQuery1)@}}|
|results|{{ref_issues(-q=MyCustomQuery1)}}|
|\2. *3. list up issues tickets that contain 'sorting' in subject*|
|notation|{{@ref_issues(-f:subject ~ sorting)@}}| |notation|{{@ref_issues(-s=sorting)@}}|
|results|{{ref_issues(-f:subject ~ sorting)}}| |results|{{ref_issues(-s=sorting)}}|
|\2. *4. *2. list up issues tickets that contain 'sorting' in subject. and specify display column(subject,author,assigned_to,status)*|
|notation|{{@ref_issues(-f:subject ~ sorting, subject, author, |notation|{{@ref_issues(-s=sorting,subject,author, assigned_to, status)@}}|
|results|{{ref_issues(-f:subject ~ sorting, subject, author, |results|{{ref_issues(-s=sorting,subject,author, assigned_to, status)}}|
|\2. *5. *3. list up tickets that contain 'sorting' in subject, and restrict by project=Wiki Lists*| project=wiki_lists*|
|notation|{{@ref_issues(-f:subject ~ sorting, -f:project = Wiki Lists)@}}| |notation|{{@ref_issues(-p=wiki_lists,-s=sorting)@}}|
|results|{{ref_issues(-f:subject ~ sorting, -f:project = Wiki Lists)}}| |results|{{ref_issues(-p=wiki_lists,-s=sorting)}}|
|\2. *4. use custom query by ID*|
|notation|{{@ref_issues(-i=9)@}}|
|results|{{ref_issues(-i=9)}}|
|\2. *5. use custom query by name*|
|notation|{{@ref_issues(-q=MyCustomQuery1)@}}|
|results|{{ref_issues(-q=MyCustomQuery1)}}|
|\2. *6. pickup issues that have subject=Sample, use custom query and put linked ID*| restrict by usr_id=89*|
|notation|{{@ref_issues(-f:subject = Sample, -l=id)@}}| |notation|{{@ref_issues(-i=9,-f:assigned_to_id=89)@}}|
|results|{{ref_issues(-f:subject = Sample, -l=id)}}| |results|{{ref_issues(-i=9,-f:assigned_to_id=89)}}|
|\2. *7. pickup issues display linked string that have subject=Sample, and put markuped description*| is results of custom query*|
|notation|{{@ref_issues(-f:subject = Sample, -t=description)@}}| |notation|{{@ref_issues(-i=9,-l)@}}|
|results|{{ref_issues(-f:subject = Sample, -t=description)}}| |results|{{ref_issues(-i=9,-l)}}|
|\2. *8. put number display linked string(=ticket id) that is results of issues that contain 'sorting' in subject*| custom query*|
|notation|{{@ref_issues(-f:subject ~ sorting, -c)@}}| |notation|{{@ref_issues(-i=9,-l=id)@}}|
|results|{{ref_issues(-f:subject ~ sorting, -c)}}|
h2. history
→ "Roadmap":/projects/wiki_lists/roadmap?completed=1
|results|{{ref_issues(-i=9,-l=id)}}|