• Force the connection on a Jira instance

      From the Organisation tab, the administrator can choose to force the connection on a Jira instance.

      From the Integration management section choose the option Forced connection on a given instance.

      Forcer_instance_Jira.png

      The editing dashboard is displayed to enter the Jira instance URL of your choice.

      • If Klaxoon does not recognize the Jira URL or the version of Jira is unknown, you will be asked to select between two authentication protocols.

      forcer_instance_jira2.png

      Click on Next

      • If Klaxoon detects the server version based on Jira URL, continue the configuration.

      For OAuth1 on Jira Cloud and Server DataCenter (version higher than v8.22)

      The configuration page of the integration between Klaxoon and Jira is displayed.

      forcer_instance_Jira3_modif.png

      Click on Connect if you are the Jira administrator, or ask your Jira Admin to send you these information.

      The Jira administrator can find these information in the Jira settings:

      forcer_instance_jira4.png

      In the tabProducts, click on Application links then, on Create a link

      The link creation page is displayed, enter the URL https://app.klaxoon.com in URL Application :

      forcer_instance_jira5.png

      Click on Continue

      A pop-up is displayed, enter the name if the application with "Klaxoon Board":

      forcer_instance_jira6_modif.png

      Click on Continue.

      The application link is created

      Forcer_instance_jira7.png

      Click at the end line of the "Klaxoon Board" application on the three horizontal dots

      forcer_instance_jira8.png

      Click on Edit

      Click on "Incoming authentifaction" section

      forcer_instance_jira9.png

      Enter the "Consumer Key" and "Consumer Name" from the data provided by Klaxoon

      Enter the "Public Key" from the data provided by Klaxoon

      forcer_instance_jira10.png

      Scroll down and click on Save

      Once the application link is created, go back to the console mode in Klaxoon and click on Connect

      forcer_instance_jira12_modif.png

      When the configuration is complete, a green tick appears on the gear wheel

      forcer_instance_jira13.png

      For OAuth2 on Server DataCenter (version higher than v8.22)

      The configuration page of the integration between Klaxoon and Jira is displayed.

      forcer_instance_jira14_modif.png

      Step 1:Once the link between applications is created, setup the application link between Jira and Klaxoon.

      The Jira administrator can find these information from their Jira settings.

      Step 2: There are two options:

      • The automatic mode
      • The manual mode: in this case, simply copy the link provided and forward it to the to the Jira administrator to create the associated webhook
      The creation of the webhook remains dependent on the Jira administrator role (or not) of the person performing the Jira import. The user on the Board remains free to choose the Jira instance on which they want to import and is autonomous.

      The Jira administrator finds the information required at step 1 in his Jira settings:

      forcer_instance_jira15.png

      Create a link

      forcer_instance_jira16.png

      Select the type of application you want to connect to:

      • Atlassian product: link to Jira, Confluence, Bitbucket, Bamboo, Crowd, Fisheye et Crucible
      • External application: link to an external application using OAuth 2.0

      Select the direction :

      • Incoming : the application can access data from Jira
      • Outgoing : Jira can access data from the application

      Click on Continue

      forcer_instance_jira17.png

      From the Application link tab, enter the application name "Klaxoon Board" and the redirection URL

      Click on Save

      forcer_instance_jira18_modif.png

      Complete the configuration by copying / pasting the OAuth 2.0 credentials (Client ID and Client Secret) on the Klaxoon configuration page.

      When the configuration is complete, a green tick appears on the gear wheel

      forcer_instance_jira13.png

    • Allow connection to Jira by personal token

      From the Organization tab, the administrator can choose to authorize the connection of the users of his console with a personal token.

      In Integration management section select the option Free login with personal token.

      connexion_libre_jira1.png

      From their Board, the Pro user can import a project from Jira.

      Click on Insert on the toolbar at the bottom left of the Board.

      Click on Jira

      connexion_libre_jira2.png

      The connection page with Jira is displayed:

      connexion_libre_jira3_modif.png

      To gather the Jira connection data, connect to your Jira account and create an API token from your settings.

      connexion_libre_jira4.png

      Click on Create API token

      The creation page is displayed, create a nom for this token an click on Create

      connexion_libre_Jira5.png

      Once the token is created click on Copy

      Go back to Klaxoon and past the API token

      connexion_libre_jira6_modif.png

      Once the form is completed, click on Save

       

      Synchronization of tickets and ideas between Jira and Klaxoon

      In order for tickets to be synchronized in both directions, i.e. from Klaxoon to Jira and from Jira to Klaxoon, you must have the Full Admin status.

      With a simple Admin status, the synchronization of tickets is only done in one direction: an idea submitted on the Klaxoon Board will appear in Jira, but a ticket created in Jira will not appear on the Klaxoon board.

      For more information on two-way synchronization contact our support team via: Help__2_.png.