プロジェクト

全般

プロフィール

操作

Wiki Lists en » 履歴 » リビジョン 10

« 前 | リビジョン 10/16 (差分) | 次 »
Tomohisa Kusukawa, 2015/11/23 13:28


Redmine Plugin: Wiki Lists
マクロ count の実行中にエラーが発生しました (Validation failed: Page はすでに存在します)

日本語は こちら.

This plugin adds wiki macros that display ticket lists.

Links

redmine.org: http://www.redmine.org/plugins/redmine_wiki_lists
repository: https://github.com/tkusukawa/redmine_wiki_lists
downloads: https://github.com/tkusukawa/redmine_wiki_lists/releases

Installation

  1. Download zip file from GitHub
  2. Unzip
  3. Move the unziped folder into the $REDMINE/plugins/
  4. Restart REDMINE

Usage

ref_issues

ref_issues macro displays list of issues.

Syntax

{{ref_issues([option].., [column]..)}}

options:

superseded 表示

  • -i=CUSTOM_QUERY_ID
    Use custom query by id.
  • -q=CUSTOM_QUERY_NAME
    Use custom query by query name.
  • -f:ATTRIBUTE OPERATOR [VALUE[|VALUE...]]
    filter. Attributes are shown below.
     
    [ATTRIBUTE]
    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_*
    

    [OPERATOR]
    =: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, 
    

You can specify two or more select option, it affect AND condition.
If you use this macro in a Issue, you can use the field value 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
    number of issues.

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

example

1. use custom query by ID
notation {{ref_issues(-i=9)}}
results
2. use custom query by name
notation {{ref_issues(-q=MyCustomQuery1)}}
results
3. list up issues that contain 'sorting' in subject
notation {{ref_issues(-f:subject ~ sorting)}}
results
4. list up issues that contain 'sorting' in subject. and specify display column(subject,author,assigned_to,status)
notation {{ref_issues(-f:subject ~ sorting, subject, author, assigned_to, status)}}
results
5. list up tickets that contain 'sorting' in subject, and restrict by project=Wiki Lists
notation {{ref_issues(-f:subject ~ sorting, -f:project = Wiki Lists)}}
results
6. pickup issues that have subject=Sample, and put linked ID
notation {{ref_issues(-f:subject = Sample, -l=id)}}
results 1389
7. pickup issues that have subject=Sample, and put markuped description
notation {{ref_issues(-f:subject = Sample, -t=description)}}
results

This is the issue[#1389]'s description that explain 'ref_issues' wiki macro example.

refer issue's field value
notation {{ref_issues(-f:issue_id = 1389, -t = cf_2 )}}
results

SampleY

use field value for filter condition
notation {{ref_issues(-f:subject = [cf_2])}}
results
8. put number of issues that contain 'sorting' in subject
notation {{ref_issues(-f:subject ~ sorting, -c)}}
results 3

history

Roadmap

Tomohisa Kusukawa さんが8年以上前に更新 · 10件の履歴