Wiki Lists en » 履歴 » リビジョン 7
« 前 |
リビジョン 7/16
(差分)
| 次 »
Tomohisa Kusukawa, 2015/05/11 15:57
Redmine Plugin: Wiki Lists ¶
日本語は こちら.
This plugin adds wiki macros that display ticket lists.
Downloads¶
bitbucket: https://bitbucket.org/tkusukawa/redmine_wiki_lists/downloads
Installation¶
- Download zip file from bitbucket
- Unzip
- Move the unziped folder into the $REDMINE/plugins/
- Restart REDMINE
Usage¶
ref_issues¶
ref_issues macro displays list of issues.
Syntax¶
{{ref_issues([options].., [column]..)
}}
options:
- -s[=WORD[|WORD]..]
select issues that contain WORDs in subject.
- -d[=WORD[|WORD]..]
select issues that contain WORDs in description.
- -w[=WORD[|WORD]..]
select issues that contain WORDs in subject or description.
- -p[=IDENTIFIRE]
Specify the project by identifire.
- -i=CUSTOM_QUERY_ID
Use custom query by id.
- -q=CUSTOM_QUERY_NAME
Use custom query by query name.
- -f:ATTRIBUTE[=WORD[|WORD...]]
Additional filter. Attributes are shown below.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_*
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 specify no select condition, page name of wiki or number of 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
example¶
1. list up tickets that contain 'sorting' in subject | |
notation | {{ref_issues(-s=sorting) }} |
results |
2. list up tickets that contain 'sorting' in subject. and specify display column(subject,author,assigned_to,status) | |
notation | {{ref_issues(-s=sorting,subject,author, assigned_to, status) }} |
results |
3. list up tickets that contain 'sorting' in subject, and restrict by project=wiki_lists | |
notation | {{ref_issues(-p=wiki_lists,-s=sorting) }} |
results |
4. use custom query by ID | |
notation | {{ref_issues(-i=9) }} |
results |
5. use custom query by name | |
notation | {{ref_issues(-q=MyCustomQuery1) }} |
results |
6. use custom query and restrict by usr_id=89 | |
notation | {{ref_issues(-i=9,-f:assigned_to_id=89) }} |
results |
7. display linked string that is results of custom query | |
notation | {{ref_issues(-i=9,-l) }} |
results | add [current_project_id] for value field can not use custom fields even when restrict the project filter by enum value of custom field: key value list overwrite_sql_for_fieldをRedmine2.0に合わせる ref_issues with custom fields not working ref_issues: Query with custom field. use custom field to additional filter want to use field reference of Issue in History part |
8. display linked string(=ticket id) that is results of custom query | |
notation | {{ref_issues(-i=9,-l=id) }} |
results | 1446 1443 1497 1063 1326 999 1248 1482 |
Tomohisa Kusukawa さんが約9年前に更新 · 7件の履歴