Sample Configuration
# Used to determine the number of dates to show in the report
: NUM-DATES 15; # Number of dates in the status history
: DATE-INTERVAL 2; # Number of days between dates
: END-DATE TODAY; # The right-most date in the status history
# The maximum number of tickets to show in the report (Click refresh button after changing this)
: MAX-TICKETS 25;
# The JQL used to find the parent tickets (Click refresh button after changing this)
: PARENT-JQL ["project = " jira.PROJECT-KEY " and issuetype=Story and updated >= -30d order by updated DESC"] CONCAT;
# Used to order the tickets in the report by status
: STATUS>ORDER [
["BLOCKED" 1]
["IN PROGRESS" 2]
["DONE" 3]
["TO DO" 4]
] REC SWAP UPPERCASE REC@ 100 DEFAULT;
Reference
Config Word | Description | Notes |
|---|---|---|
| This sets the number of status history date chips to render for each ticket | |
| This sets the step size in days in between each date interval | Each status chip covers a date range starting from its date and extending through the number of days of the |
| This is the rightmost date of the status history | This takes any valid Forthic date such as a date literal or a word that returns a date (e.g., |
| This sets the number of tickets to render in the report. | After changing this value, click the refresh button to pull fresh data. |
| This specifies the JQL used to pull tickets for the report | By default this pulls Story tickets in the current project that have been updated within the past 30d. |
| This defines a sort order for the tickets based on Status. | If you just want to specify an order, focus on the following rows and revise the Statuses to match your project. ["BLOCKED" 1] ["IN PROGRESS" 2] ["DONE" 3] ["TO DO" 4] This definition follows the Forthic idiom of transforming one thing into another. |
0 Comments