Teamworkx Issue Publisher for Jira

The Teamworkx Issue Publisher from catworkx automatically creates and updates pages in Confluence and inserts arbitrary field values of Jira issues at freely definable positions on these pages. Thus, the Teamworkx Issue Publisher not only enables the automatic creation of process or project documentation (e.g. “What’s new” pages), but can also be used to trigger the creation of offers, contracts and invoices from within the Jira application.

Many companies already use Confluence for documentation – as a supplement to their Jira application. When Atlassian speaks of “integration of both systems”, it means first and foremost that requirements definitions and product specifications are maintained in Confluence. Links to the corresponding Jira processes are inserted at the appropriate place. In the opposite direction there is only the possibility to link from a Jira process to an existing Confluence page.

With the Teamworkx Issue Publisher, catworkx provides an app that can be used to trigger the creation or update of a Confluence page from a Jira application. Three ways of publishing are supported:

  • Automated via a post-function during a status transition
  • Automated for operation events, e.g. after updating an operation
  • Manually via “Publish Issue” operation in the “More” menu of the task view

The appearance of the Confluence pages is determined in advance by creating template pages in Confluence. For the formatting of a page, all possibilities that Confluence offers are available. A placeholder is inserted on the page at the places where process data is to be output later. If it is already clear when creating the template that the target page will only be created once or will be completely overwritten later on during an update, a variable is sufficient as placeholder. However, if it is certain that only the values from the Jira processes are to be updated during an update, the supplied Jira Field Value Macro for Confluence is to be used as a placeholder.

The template pages are imported via the template management of the Teamworkx Issue Publisher.

When executed via workflow transition or case action, the Teamworkx Issue Publisher creates a new Confluence page or page version. Placeholders inserted in the template are replaced with the actual field values of the issue. The Confluence page versioning feature allows you to refer back to older documentation at any time to keep up to date with the development of the issue.

With the Teamworkx Issue Publisher for Jira it is also possible to create PDFs directly on the Jira issue. This is done via a PDF export option, with a pre-installed standard template.

The generated PDFs based on HTML templates are uploaded as attachments to the issue and can optionally be moved to a Confluence page using the Move Attachment operation.

Functions

  • Configurable operations that can be triggered manually, automatically by operation events or via a post function
  • Create and update Confluence pages and blog entries
  • Move or copy attachments from a Jira operation to the corresponding Confluence page
  • Sending e-mails or web requests from one process
  • Create PDF files or text-based files
  • Freely designable templates directly in Confluence
  • Differentiation of templates for the publication of single or multiple transactions
  • Confluence macro, which is replaced by field values by Jira
  • Publishing Jira information to a custom field using a template
  • Output of Insight objects on Confluence pages

30 day free trial

In the Atlassian Marketplace all Teamworkx Apps are free for you to test.

Marketplace

Prices

Documentation

App support

Contact us!

We will be happy to inform you in a free initial interview about the advantages and benefits of Teamworkx products for your company.
Contact us

    Please fill in all marked fields (*).

    Information on the processing of your personal data can be found in our
    Data protection declaration
    .

    Loading...