Please watch introduction video to see what this addon can do for you.
Every Confluence Field custom field that you create in your JIRA application should be configured. Below is a sample configuration dialog screenshot:
In case that your JIRA is linked to multiple Confluence instances you may use the Confluence field to specify the instance that you want to provide data for your custom field. By default it will use the primary Confluence instance.
You may specify CQL (Confluence Query Language) clause to filter Confluence pages according to your requirements. The clause will be applied to every query that your JIRA executes. For example, if you set your field’s filter value to space=”DS” and label=”client” and type mesilat while editing the custom field, than the resulting CQL-query will be type=”page” and title~”mesilat” and space=”DS” and label=”client”. The field’s dropdown control will list only those Confluence pages that match this query.
Use this field to test your Confluence connection and your CQL-filter validity. If your JIRA is authorized to call the Confluence instance’s API and your filter is valid than you will get a list of Confluence pages that match your query. The test field behaves exactly the same way as your custom field when you edit a JIRA issue.
If your JIRA is not authorized by Confluence than you will get an error: To fix the error please follow the link provided in the message to start the OpenID “dance” and authorize your JIRA. It should be noted that authorization is individual for every JIRA user.
If your filter CQL is invalid you will get a syntax error: Refer to Confluence documentation (or use the link provided above) to fix the error.