JIKI - Embed a list of issues from a JIRA instance into a Mediawiki wiki page.
In mediawiki LocalSettings.php specify the JIRA Hostname:
$jikiJiraHost = "https://jira.atlassian.com";
Specify the JIRA User Name:
$jikiJiraUser = "[email protected]";
Specify the JIRA User Password:
$jikiJiraPassword = "ILoveC@ts";
Specify any custom fields you have in your JIRA:
$jikiExtraParams = array
(
array("param"=>"myParamNameInWiki","jql"=>"\"My Field Name in JIRA\""),
);
In any wiki page include the following tag:
<jira></jira>
As long as the field is a basic JIRA field or you have configured it in LocalSettings:
<jira project="GO,FP,HELP"></jira>
<jira project="SUPPORT" status="In Progress,!Closed,!Resolved"></jira>
Search for text in the issue's text fields:
<jira>text to search for</jira>
Search multiple fields:
<jira project="GO" reporter="gvoss"></jira>
Allow subtasks to be returned when not using JQL:
<jira key="ABC-123" jikiAllowSubtasks="true"></jira>
Or for an advanced user or where the JIKI implementation of JQL is insufficient:
<jira jql="project = GO AND reporter in (gvoss)"></jira>
If you wish to use greater than (>
) or less than (<
) you must escape these:
<jira jql="project = CAT AND createdDate >= 1970-01-01"></jira>
Ordering can be done by using the orderby
parameter:
<jira orderby="updateddate ASC"></jira>
or by including it in your JQL:
<jira jql="ORDER BY updateddate ASC"></jira>
- id - synonymous with key
- key - the Key of the issue (e.g. ABCD-1234)
- issuetype - the type of issue (e.g. bug)
- project - the key of the project (e.g. ABCD)
- fixversion - the fix version (e.g. 1.0.0)
- affectedversion - the affected version (e.g. 1.0.0)
- reporter - username of the reporter (e.g. gvoss)
- assignee - username of the assignee (e.g. gvoss)
- status - name of the status (e.g. In Progress)
- sprint - ID or exact name of the sprint (e.g. 786)
- resolution - status of the resolution (e.g. resolved)
- labels - any labels applied to the issues (e.g. cats)
- component - any components applied to the issues (e.g. content management)
- epiclink - name of the epic link (e.g. loading screen)
The following parameters exist to allow controlling of format:
- jikiformat - allows you to control the formating (default: html)
<jira jikiformat="simple"></jira>
<jira jikiformat="html"></jira>
<jira jikiformat="html.table"></jira>
<jira jikiformat="html.bullets"></jira>
<jira jikiformat="html.numbered"></jira>
- jikifulldetails - allows you to control how much detail is printed to the screen
<jira jikifulldetails="true"></jira>
In LocalSettings.php you can specify additional Curl Opts to apply:
$jikiCurlOpts = array(CURLOPT_SSL_VERIFYPEER => false);
You can also configure some defaults for the renderers:
$jikiRenderDefaults = array();
$jikiRenderDefaults["html"] = array("target" => "_self");