Add topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.
Extra information
System documentation:
Atlassian Jira Server
Connector Package Documentation
Setting up HTTP Client Atlassian Jira Server
Steps
- In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select Atlassian Jira Server HTTP Client as the prototype of the HTTP Client.
- Fill in the Base URI and Authentication Type
- Basic
- Fill in Username and Password (Replace Password with API Token).
- PATs
- Fill in the Bearer Token
- Save.
Subscribing to Entities from Atlassian Jira Server
Steps
- Go to Connections → Incoming and create a new incoming configuration and select Atlassian Jira Server Subscriber as the subscriber.
- Select the entity you want to subscribe from Atlassian Jira Server.
- Add any request parameters needed to subscribe to the entity (optional).
- You can optionally add a transformer to transform the request parameters into something you need.
- Select the Atlassian Jira Server HTTP Client to use.
General Concept
We follow Atlassian Jira Server documentation on building this connector so you can easily use the connector based on Atlassian Jira Server API Reference.
Entity
It’s the entity you want to subscribe to from Atlassian Jira Server. Please refer to the entities in Management APIs from the Atlassian Jira Server API Reference page.
Request Parameters
These are the parameters you can provide to get the needed entity based on Atlassian Jira Server API Reference. Please look at the example below on how to fill the Request Parameters field when calling “Get project category by id” entity
That’s why we need to define the id property inside the path property in the Request Parameters field. The properties inside query parameters will be parsed as query parameters. Here is the final URL that will be called when using such Request Parameters field on Get project category by id.
/rest/api/2/projectCategory/abc
Input Transformer
Any transformers set here will be executed after the Request Parameters are loaded. So, you basically can add any transformer to provide and transform the request parameters into anything you need either as path parameters and/or as query parameters of an entity.
HTTP Client
It’s the HTTP Client configuration or prototype you will use to access Atlassian Jira Server.
Publishing Entity to Atlassian Jira Server
Steps
- Go to Connections → Outgoing, create a new outgoing configuration, and select Atlassian Jira Server Publisher as the publisher.
- Select the action that you want the publisher to do with the data.
- Select the Atlassian Jira Server entity you want the data to be published.
- Select the HTTP Client to use.
General Concept
Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration).
Action
Currently, we support Create (HTTP POST method), Put (HTTP PUT method), and Delete (HTTP DELETE method).
Entity
We support publishing to most Atlassian Jira Server endpoints. Please refer to the entities in Management APIs from the Atlassian Jira Server API Reference page. Based on the documentation, some endpoints may need one or more path parameters.
For endpoints that require an object as the request payload, please look at the example below. For example, we want to Create project category. Please select “Post” as the action and “Create project category” as the entity of the publisher.
You can put the payload you want to send to Atlassian Jira Server into the payload property in the data, Here’s the Example of payload and response.
Alumio will send an API request to Atlassian Jira Server with URL /rest/api/2/projectCategory
HTTP Client
It’s the HTTP Client configuration or prototype you will use to access Atlassian Jira Server.