Requirements

The following requirements apply to the use of PLANTA project with Jira:

  • PLANTA project must be installed (at least DB 39.5.15)
  • Jira (Server) must be installed
  • PLANTA link must be licensed
  • PLANTA Jira link must be licensed

PLANTA offers a connection to Jira Server by default. An individual connection to Jira Cloud is possible. For this purpose, please contact your PLANTA consultant.

Settings

To enable the integration of PLANTA project with Jira, the following settings must be made:

  • PLANTA Server
    • Configure the following server parameters for the PLANTA project system which is to communicate with the Jira system in the web.conf:
      • generic_service - must be activated (true)
      • generic_service_interface - must be configured if necessary
      • generic_service_port - must be configured
      • ssl_generic_enable - must be activated (true) if you want to run Jira on HTTPS.
      • apikey_auth_filter_generic - must be deactivated (false) because Jira does not authenticate itself to the web interfaces.
        • After you have configured the parameter you have to restart the server.
  • PLANTA link
    • Define the required parameters in the Jira authentication area in the Jira Parameters module and select the required interfaces in the Jira interfaces area.
      • In PLANTA standard, all required standard interfaces are already stored by default.
    • Synchronize or link PLANTA project and Jira users in the User Synchronization module.
  • PLANTA project
    • Time Recording Variant = 3 must be preset to enable the transfer of hours worked recorded in Jira to PLANTA project.
    • At the moment the interface does not support automatic reverse postings. This means
      • you can either use the Reverse Posting Variant = 0 reverse posting setting. However, this setting does not prevent changes from being made on the part of Jira (this would require adjustments to be made in Jira), the changes will simply not be transferred to PLANTA project.
      • or you can generally work without reverse postings (no key date, no release for records transferred to external systems, etc.)

Note