FAQ & Troubleshooting

Spaces may claim to be "Unavailable", indicating either that

• the permissions on the space have changed and you may no longer access it
• the space has been deleted from Confluence

• If there is the possibility that another Jira administrator has configured this, and that the space they have selected is not available to you, please check with them. 

• Check the status of the Confluence server. If the server is available, ask an administrator about the status of the Confluence space if you know which space it should be.

• If the space has been deleted, you can edit the Page Configuration to select a different space. Note that, since the space is unavailable to you, the select box will already show a different one since the field cannot be blank.

The Page Configuration status shows an error and the configuration has been disabled

The error status may show up if the Page Content used by this configuration has been deleted (the column Page Content should also be blank). 

In this case, the configuration will also be disabled by the system. It is not possible to activate it again unless it is edited first.

• Edit the configuration and select a different Page Content to use or
• Create the Page Content you need

If the application link does not work, it should be checked whether the Auth is set to "OAuth" which is incorrect, or is set up with "OAuth (with impersonation)" which is correct.

Check, if your Page Configuration is activated. After editing it is deactivated and has to be activated manually

Check the JQL-Filter in your Page Configuration. You can click on the filter shown in the column JQL in the Page Configuration list to check the filter results.

By Confluence rules, a page title must be unique within a space.

• One solution may be to create the page again under a different title
• If the title field is disabled, please contact a Jira administrator for this problem

The page is created in Confluence, but the Page title is shown as "undefined" in Jira and the link is not created.

• Check if linking of issues is permitted in your Jira system, as described here Atlassian - Configuring issue linking
• See if your user has permission to create links

The Create Page post function may currently throw the following error: Could not load Function Provider class

Steps to reproduce:

1. After installing version 2.4, transition any issue that utilizes the Create Page post function

Error description:

• An error dialog opens with the error message "Could not load Function Provider class"
• Jira logs contain the following:

Could not load class 'de.greenique.jira.pageprint.workflow.CreatePagePostFunction' java.lang.ClassNotFoundException: de.greenique.jira.pageprint.workflow.CreatePagePostFunction

Resolution:

• Open the affected workflow, delete and reconfigure the post function

It is currently not possible to create several Confluence pages sequentially from the same issue if you change any issue fields in between. 

Steps to reproduce:

1. Create a page via the Documentation panel in your issue
2. Do an inline change on any issue field (for example, the issue description) and save
3. Open the Create Page dialog again 

Error description: 

• Parent page and title fields in the Create Page dialog box will not update when changing the configuration option
• An error occurs when attempting to create a page with this dialog box
• No page is created in Confluence

Workaround:

After creating a Confluence page, reload the issue screen in your browser.

When creating or editing an Issue to Page Configuration item, the field named Global space: Parent page may behave inconsistently.

Steps to reproduce

1. Create a new  Issue to Page Configuration item by clicking on the Add configuration button
2. Scroll down and view the Global Space: Parent page toggle - the slider may be set to active, but there is no select box underneath it for choosing said page

Error description

• The switch in a new configuration or a configuration that existed prior to installing version 1.3.x is set to active when first viewed
• The error is merely a visual problem and will not affect your configuration data.

Workaround

Deactivate the toggle, and reactivate it. The select box for the parent page should now appear and both fields will behave as intended after you save the configuration for the first time.

A solution for this problem has been established and will be available with version 1.4.

When switching issues in the navigator view, the Parent Page and Title are not loaded correctly in the dialog box.

Steps to reproduce

1. Open the issue navigator (Top Menu Bar → Issues → Current Search or Search for issues)
2. Select the first issue and click on "Create page" in the Documentation panel
3. Close the dialog box, select another issue and click on the "Create page" button 

Error description

• The options and data displayed in the dialog box do not match the issue selected

Workaround

Close and reopen the dialog box. The error occurs because the documentation panel is not fully loaded by the time the issue has finished loading.

A solution for this problem is in development for version 1.5.

When an issue is transitioned using a project automation, the Create Page post function will not replace custom field variables in the resulting Confluence page.

Steps to reproduce:

1. Create a template that uses Jira custom fields, Profields or Insight variables
2. Add the Create Page post function to a transition in your Jira workflow
3. Create a project automation with Automation for Jira that triggers the transition
4. Check the Confluence page created via the automation

Error description: 

• Confluence page displays variables instead of values of custom fields

Resolution:

• Starting with version 2.3.1, standard Jira custom fields are working as expected
• Projectrak and Insight variables are incompatible and cannot be filled when using a project automation as of this time