New Features:

• Manual execution of operations

Improvements:

• Show the version numbers on the manage servers page

Bugfixes:

• The link to show the usage of templates was not working

Bugfixes:

• Fixed issue related variables not working in the additional issues JQL of a multi issue operation

Bugfixes:

• Fixed issue related variables not working in the additional issues JQL of a multi issue operation

Bugfixes:

• Fix problem with saving the general settings when Zephyr is installed

Bugfixes:

• Fix problem with saving the general settings when Zephyr is installed

New Features:

• Use the updated $issueHelper and $projectHelper variables to access issue and project properties

Improvements:

• Introduced workaround to fix problems with our code editors when Insight is installed

New Features:

• Use the updated $issueHelper and $projectHelper variables to access issue and project properties

Improvements:

• Introduced workaround to fix problems with our code editors when Insight is installed

New Features:

• Velocity code highlighting for templates and other inputs using variable replacement
• Optionally skip validation of status code for web requests

Improvements:

• Horizontal navigation bar on configuration pages

New Features:

• Velocity code highlighting for templates and other inputs using variable replacement
• Optionally skip validation of status code for web requests

Improvements:

• Horizontal navigation bar on configuration pages

Change:

• Actions (within an operation) are now called steps

New Features:

• Use the updated $issueHelper variable to access an issues generic web links or its remote Jira issue links

Bugfixes:

• The validation of the project filter for operations was not working correctly. This problem was introduced in version 11.1.0 and only affected Jira instances with more than 400 projects.

Change:

• Actions (within an operation) are now called steps

New Features:

• Use the updated $issueHelper variable to access an issues generic web links or its remote Jira issue links

Bugfixes:

• The validation of the project filter for operations was not working correctly. This problem was introduced in version 11.1.0 and only affected Jira instances with more than 400 projects.

New Features:

• Select which operations, templates and other settings to import during the configuration import
• Upload the configuration for the import directly via the web interface
• All admins (not just system admins) can now export and import the configuration
• Set the value of a variable field (e.g. via if-then-else logic) in the Set field value action

Improvements:

• Optionally send an Issue Updated event (containing the updated field) in the Set field value action
• General security improvements

Bugfixes:

• Fixed a potential problem when deleting a temporary file during PDF creation on a Windows server

New Features:

• Select which operations, templates and other settings to import during the configuration import
• Upload the configuration for the import directly via the web interface
• All admins (not just system admins) can now export and import the configuration
• Set the value of a variable field (e.g. via if-then-else logic) in the Set field value action

Improvements:

• Optionally send an Issue Updated event (containing the updated field) in the Set field value action
• General security improvements

Bugfixes:

• Fixed a potential problem when deleting a temporary file during PDF creation on a Windows server

New Features:

• Reorder the actions of your operations
• Use the updated $responseHelper variable in your templates to parse a JSON response or string as Map or List

Improvements:

• Optionally enter names for your actions for easier recognition
• Show more information about the operation when viewing the Publish Issue Using Operation post function
• Show in which operations your templates are used
• Show the name of the operation, action, template or server when deleting it

New Features:

• Reorder the actions of your operations
• Use the updated $responseHelper variable in your templates to parse a JSON response or string as Map or List

Improvements:

• Optionally enter names for your actions for easier recognition
• Show more information about the operation when viewing the Publish Issue Using Operation post function
• Show in which operations your templates are used
• Show the name of the operation, action, template or server when deleting it

New Features:

• Retrieve a file using a generic web request and save it as an attachment or use it in the operation
• Create a Zip file from attachments of the current issue or files retrieved or created during the operation
• Let the user download files retrieved or created during the operation (instead or in addition to saving them as an attachment on the issue)
• New Publish button (next to the Share and Export buttons) that can be used in addition or as an alterative to the exiting button (in the More menu of the issue)
• Use the updated $confluenceHelper variable in your templates to get a Confluence page from a URL
• The Set page restrictions, Add page restrictions and Copy attachments from page actions are now fully supported

Improvements:

• URL input fields to select a page do now support all Confluence Cloud page URLs

New Features:

• Retrieve a file using a generic web request and save it as an attachment or use it in the operation
• Create a Zip file from attachments of the current issue or files retrieved or created during the operation
• Let the user download files retrieved or created during the operation (instead or in addition to saving them as an attachment on the issue)
• New Publish button (next to the Share and Export buttons) that can be used in addition or as an alterative to the exiting button (in the More menu of the issue)
• Use the updated $confluenceHelper variable in your templates to get a Confluence page from a URL
• The Set page restrictions, Add page restrictions and Copy attachments from page actions are now fully supported

Improvements:

• URL input fields to select a page do now support all Confluence Cloud page URLs

New Features:

• Escaping for CSV files, that are created via the Create a text based file action
• Use the updated $issueHelper variable to get the page ID from Confluence wiki links, e.g. $!issueHelper.getPageIdFromFirstConfluenceLink($issue)

Improvements:

• Better handling of leading and trailing whitespaces in the title of a page when creating a new Confluence page

Note: We intend to launch a Data Center approved version of the Teamworkx Issue Publisher in December 2020. Customers running Jira in a Data Center Deployment using Issue Publisher Server will be required to purchase a Data Center app license upon their next renewal!!!

Improvements:

• PDF files now support images attached to the issue (e.g. in the description or comments)

Note: We intend to launch a Data Center approved version of the Teamworkx Issue Publisher within the next three month. Customers running Jira in a Data Center Deployment using Issue Publisher Server will be required to purchase a Data Center app license upon their next renewal!!!

New Features:

• Create PDF files from HTML based templates
• Create text based files (e.g. markdown files)
• Move Confluence pages

Improvements:

• Show the updated date for operations and templates
• Small UI improvements

Note: The Publish Issue post function is now deprecated, use the Publish Issue Using Operation post function instead.

Note: We intend to launch a Data Center approved version of the Teamworkx Issue Publisher within the next three month. Customers running Jira in a Data Center Deployment using Issue Publisher Server will be required to purchase a Data Center app license upon their next renewal!!!

New Features:

• The new display format column-view-html for the field value macro displays values like they're shown in the issue navigator (including working links)
• Use the new $valueCollector variable to save multiple values in a custom field

Improvements:

• URL input fields to select a page do now support (most) Confluence Cloud page URLs
• The user display formats of the field value macro (e.g. user-mentioning) do now support multi user picker fields

Note: Some of these features/improvements require the newest version of the Teamworkx Issue Publisher Macros for Confluence app

New Features:

• Create blog posts
• Optionally exclude old attachment versions when sending attachments to Confluence or via mail

Improvements:

• Attachments are send to Confluence in the order they where created in Jira (from oldest to newest)
• Access the last Confluence page in a non-Confluence action (e.g. Create comment) using the $currentPage variable

New Feature: New and extended helper for variable replacement:

• Use the new $collectionHelper variable to easily handle collections
• Use the updated $issueHelper variable to access issue work logs
• Use the updated $fieldHelper variable to format durations (e.g. from work logs)
• Use the updated $userHelper variable to get the display names of a collection of users at once (e.g. the value of a multi user picker field)
• Use the updated $insightHelper variable to access the comments and the history of an object (see also How to publish an Insight object including its comments and history)

New Features:

• Send an email containing attachments from the issue
• Filter attachments by their name, size or date when copying or moving them to a page or when sending them in an email
• New Create web link action

Bugfixes:

• The Publish Issue post function did not use the default Confluence server as a fallback. Manual and automated operations as well as the Publish Issue Using Operation function where not affected.

New Features:

• Copy or move the attachments of multiple issues to a Confluence page at once
• Create links from multiple issues to a Confluence page
• Set a field value, create a comment, send an e-mail or send a web request for each issue within a multi issue operation
• Configure if you want to execute an action for the main issue and/or the additional issues in a multi issue operation

Bugfixes:

• Fixed a potential problem with the operations cache in a clustered environment

• New Feature: Automate operations using event based triggers
• Bugfix: The anybody permission checkbox could not be deselected in the add or edit operation screens

New Features:

• The Send Mail action is now fully supported
• New user-profile formatting option for the field value macro

Improvements:

• A user that prefers text mails will receive an HTML mail instead of an empty mail if the mail template only has an HTML body and no text body
• The field value macro now shows the field name when viewing a template page (when the issue parameter and the body are empty)

Note: Some of these features/improvements require the newest version of the Teamworkx Issue Publisher Macros for Confluence app

New Features:

• Make a web request within an operation (including a new default template to create a Confluence space)
• Access the response of a web request using the new $response and $responseHelper variables
• Create a Jira comment within an operation

Improvements:

• Several small UI improvements

• Improvement: Optionally update an existing page in the Create Page action within an operation
• New Dark Feature: Publish an issue via mail using the new Send Mail action within an operation

• Significant performance improvements for JQL filter in larger Jira instances

New Features:

• Create or update pages in Confluence without the need for an application link
• Add or set page restrictions using an operation (this was already possible in the Publish Issue post function)
• Add a Confluence user macro to a page using $macroHelper.getUserProfileMacroBody(userOrName)
• Get the Confluence user key for a Jira user using $confluenceHelper.getUserKey(userOrName)

Improvements:

• Initialize the body of Jira Field Value macros for other issues than the main issue when using $macroHelper.getFieldValueMacroBody
• Initialize the body of Jira Field Value macros for the additional issues
• Evaluate the parent page advanced format later, to enable e.g. accessing stored page IDs from previous actions

• Bugfix: Labels are ignored when getting attachments from Confluence with the Publish Issue post function

• Bugfix: Exception in template engine when Profields is not installed

• New Feature: Access values from Profields by DEISER or search for projects using PQL using the new $profieldsHelper variable

• New Feature: Update field value macros for multiple issues at once
• New Feature: Optional asynchronous execution of operations
• Improvement: Increased timeouts for page creation and update to 60 seconds

• New Feature: Set the value of a custom field in an operation using a template
• New Feature: New individual action to set the labels of a page in an operation (this can be used together with the update field value macros action)
• New Feature: Add labels to attachments that are send to Confluence in an operation (this was already available in the Publish Issue post function)

• Bugfix: Possible exception when checking permissions of operations that have group or role permissions but not both

• Bugfix: Possible exception when getting linked issues in a template
• Bugfix: Copying an operation does not copy its actions

New Features:

• Freely define multiple actions in an operation
• Use operations in the new Publish Issue Using Operation post function
• Use the new $confluenceHelper variable in your template to get a Confluence page by its ID or space key and page title
• Optionally update the page title in the Update field value macros on page action when used in an operation
• The Create link to page action is now available in an operation
• Use a constant page ID for update actions in the Publish Issue post function

Removed Features:

• The Create Confluence Page For Single Issue Function, Create Confluence Page For Multiple Issues Function, Update Confluence Page From Template Function, Update Confluence Page Field Values Function and Move Attachments to Confluence Function post functions where removed. These were deprecated since version 7.0.3.0 from April 2017.
• The $customFieldManager and $customfield_xxxxx variables are no longer available in a template

• New Feature: Access Insight objects and their attribute values in a template with the new $insightHelper variable
• New Feature: Use a custom field (e.g. Issue Picker for Jira) to pre select the additional issues in a multi issue operation

• New Feature: More configuration options for operations such as pre selecting the additional issues or what to do after creating a new page
• New Feature: Advanced way to pre select the (parent) page in an operation
• Bugfix: Unnecessary warning in log when getting server from legacy post function configuration

• New Feature: Export and import the complete configuration (restricted to system admins)
• New Feature: REST API for all configuration items and the export and import of the complete configuration
• New Feature: Access linked issues in a template with the new $issueHelper.getLinkedIssues, $issueHelper.getInwardLinkedIssues and $issueHelper.getOutwardLinkedIssues functions
• Improvement: Better error handling
• Improvement: Field Value Macros are now initialized when using the Update (overwrite) existing page action
• Improvement: More efficient update of page labels
• Compatibility with Jira 8 (Beta) (Note: The bulk operation Create Confluence Page is disabled in Jira 8)
• Removed Feature: The Issue Panel Macro functionality has been removed. You can still view the contents of existing Issue Panel Macros, but not update them.

• New Feature: Use the new $projectHelper variable to retrieve projects by their key or ID in a template
• New Feature: Use the new functions $issueHelper.getIssue(s) and $issueHelper.findIssue(s) to retrieve issues by their key/ID or to search for them with JQL
• Bugfix: Publish issue action did not open in a pop-up after e.g. an inline edit
• Bugfix: When the publish issue action is not opened in a pop-up after completion the user is redirected to an URL containing the context path twice

• New Feature: Access the content of the current page with $currentPage in your template. This can be used to update e.g. only the page title or the labels of a page. You can also append content to an existing page.
• Bugfix: In the bulk operation Create Confluence Page there where no Confluence server selectable

• Bugfix: The publish issue action did not open in a dialog in Jira 7.10

• New Feature: Execute a post function or operation as a different user. This can be used, for example, if the logged in user does/should not have permission to edit the actual Confluence page.

• New Feature: Create a link to an existing Confluence page with the Publish Issue post function

• Bugfix: Creating pages failed when they contained Unicode emoticons.
• Bugfix: Creating a page failed when the used storage format template was completely empty.
• Bugfix: When setting page restrictions the edit users and groups where only added to the view users and groups if both view users and view groups where set.
• Note: There is also a new version of the Issue Publisher Macros for Confluence app available here.

• Bugfix: There was a problem while updating labels when using Issue Publisher 7.0.4.2 or later with Jira 7.0.x and Jira 7.1.x

• Filtering for labels when copying attachments from a page now works with all supported Confluence version (5.5 or newer) (was 6 or newer)

• Add labels to attachments moved or copied from the Jira issue to a Confluence page using the Publish Issue Post Function.
• Filter for labels when copying attachments from a page in the Publish Issue Post Function (dark feature).

• Copy attachments from Confluence Page to Jira Issue

• Filter operations by project and issue type (before showing the Publish Issue link)
• Attachments that are send to Confluence use the build-in versioning instead of appending a number to the filename
• Optionally use constant values (page ID, space key, page title) to find the parent page in the post function
• Add restrictions to Confluence pages via post function (dark feature)

• Use exiting Confluence page as a template to create new pages
• Formatting options for the Jira Field Value macro
• Several new functions for the $macroHelper to add macros to your templates
• Select a global fallback application link
• New version of the free catWorkX Issue Publisher Macros for Confluence is required for certain features

• Use the new function $fieldHelper.replace() in the templates to replace illegal characters before creating Confluence labels. This overrides the default behavior of removing all illegal characters.
• Fixed the preview links not being created when the filename contains more than one period.

• When copying or moving files to Confluence non ASCII characters in the filename aren't replaced by question marks anymore.
• Fixed the preview links not being created in certain situations (e.g. the filename containing non ASCII characters)

• Fixed the Jira Field Value macro not being updated if it previously contained an empty value
• Info: The Issue Publisher Macros for Confluence add-on does not need to be updated

• Use the issue comments in Confluence templates with $issueHelper.getComments().
• New Default Single Issue Template with Comments, use this as an example on how to handle the list of comments.
• Get the displayed value of a custom field with $!fieldHelper.getColumnViewValue(). Useful if the displayed value is different to the stored value (e.g., nFeed).
• Rework of the "Template Help" dialog and "JQL Help" dialog

• Select from all issues and not only issues from your history in the additional issue picker and the main issue picker

• New Confluence Application Link OAuth Validator
• New "Page" option in the operation configuration to let the user select a page or define a fixed page.

• Add issue panels to your created Confluence pages and update only the contents of those panels leaving the rest untouched
• Replacement of the catWorkX Jira Field Value Macro by catWorkX Issue Publisher Macros for Confluence (to use the issue panels)
  • Make sure to de-install to old Conlfuence add-on
• Changed parameter order for workflows and operations
• Page names instead of URLs are displayed in the Publish Issue action dialogs
• Prevent a field value from being escaped using $fieldHelper.doNotEscape($fieldHelper.getValue("description")).

• Support wiki markup in fields like description when creating or updating a new page
  • Use $!fieldHelper.getWikiMarkupValue("description") in your template to achieve this (see: https://plugins.extern.catworkx.de/x/rxUBAQ)
• Optionally create links to moved attachments

• Consolidate all post-functions in one
• New JQL condition to determine the execution of a post-function
• New $additionalIssuesCounter variable to count the number of iterations on a multi issue page
• "Move Attachments" is now an option within the post-function and not a single post-function
• Create single pages for multi issues (one page per issue)
• More than one link type can be selected to add additional issues in an multi issue post-function

• Show the parameters for the different post functions on the overview

• Update Confluence Page post function now works for multiple issues

• Bugfixes for nested Confluence macros in a template.

• Fixed possible error when updating the Jira Field Value macro with an empty value
• Fixed permissions not being saved when creating a new operation

• Confirm button after executing a publish issue action to reload the Jira page

• Bugfix: Using an issue field containing "&" or "<" results in the Confluence page not being created

• New "Publish Issue" action
• New operations
• New JQL filter for templates to restrict documentation generation to special issue types and projects
• New default templates
• Removed user and group restrictions from bulk operation
• Use key of the current issue if the key is empty in the catWorkX Jira Field Value Macro

Initial release