Subscribe to get all of your Dirigent.io and BMP news right in your inbox
Dirigent.io now offers you the ability to connect to any JIRA server, where you can create an issue, comment on an existing issue and log your work, within the Dirigent.io application. To do that, you need to configure a JIRA connector in Dirigent.io, which you can do two ways, via the basic connection, or by using the Oauth connection.
The basic connection means that for every action that Dirigent.io takes, a request to the JIRA server is made, using the username and password that you provided when you created the connector. In order to create a connector with the basic connection, you need to go to ‘’Settings’’, then click on ’’Connectors’’, select the type of connector as JIRA, and then select ’’basic’’ in the dropdown menu that will appear.
By submiting this dialog, a new connector will be created with four attributes, where you can set your JIRA username, password and your JIRA url (e.g. http://jira.example.com or http://www.example.com/jira). All of your data is stored in the Dirigent.io database safely, because it’s encrypted before storing. Due to the fact that JIRA uses RSA encryption for signing the API calls, when creating a new connector, Dirigent.io generates a new public and private key pair, which means that you will receive an email that contains the public key, which you will need later while you’re configuring the Application link in JIRA.
After setting the value of all of the attributes, you can apply them by creating an Application link in JIRA. You can do this by clicking on "Settings", then "Applications" and then selecting "Application links" on the left side, under "Integrations". Fill out the form like the one in the image bellow.
Now you are ready to create/update a JIRA issue through Dirigent.io task in designer.
Alternatively, you can create a JIRA connector with Oauth connection. To do that, select the "oauth" connection type in the new connector dialog. To configure an oauth JIRA connector you only have to provide your JIRA URL. Like in the basic connection example, you have to create a consumer in your JIRA settings by following the same steps as before.
The difference is that for this consumer you have to allow the 2-legged oauth. To do that you need to click "Edit" for that consumer, select incoming authentication, remove the previous configuration, reenter the consumer key, consumer name and public key, and fill out the rest of the form like the one in the image.
Now that everything is ready, the only thing left to do is to connect to your JIRA through Dirigent.io by clicking the Connect button on the Connector view. This will open an window where you can complete the connection and autorization to JIRA.
After allowing Dirigent.io to access your JIRA, you will receive a verification code, which you need to copy to the popped up dialog in Dirigent.io, as this is required to get the access token.
If everything is ok, you shoud receive successfully authorized notification. At this point the access token is stored in the database, and until it expires, Dirigent.io will be using it to access your JIRA account. When it expires, you will need to connect again to get a new access token.