Purpose of the incoming REST calls section it take care of the mapping of the data from external systems to JIRA.
It is not always possible or feasible for the other system to talk to JIRA using the native JIRA REST API.
In these cases there is a need for a translation and action based on the format that the external system sends, here is were iHUB shines!
With iHUB incoming three steps process 1. SEND TO IHUB → 2. IHUB ROUTES IN DATA TO ACTION → 3. ACTION UPDATES ISSUES ,external systems will be able to create/update JIRA data.
There is a powerful rule engine which can be used to route the incoming request to the correct action.
The action then takes the input from the incoming REST call and sends that to JIRA in the format JIRA expects.
Three step process
1. SEND TO IHUB
The external system POST data to iHUBs URL, which is stated in on the Incoming page.
URL ends with /rest/restfulintegrator/1.0/incoming
2. IHUB ROUTES IN DATA TO ACTION
iHUB rule engine is where new rules are created. Simply press New Rule button.
And specify what conditions needs to be fulfilled for the rule to pass the data to an iHUB action.
| Conditions | Description |
|---|---|
| User | Execute of the user is equal or not equal to the specified user |
| Data | Use JSON Path - Pick data from response expression to check if the payload includes the valid data before executing. |
| URL | add any query param to the POST iHUB URL, such as
To distinguish between systems. |
On the Action part select the iHUB action that will be triggered if the condition is true.
3. ACTION UPDATES ISSUES
Last part is executing the action, this is done in the same manner as all other actions.
The Payload from the external system is available as variables to use in the action.
Checkout Chained actions and JSON Path for more details.
Authentication
Use the JIRA basic auth or OAuth to access the incoming URL from an external system.
Behind firewall
There is no need to open up the full JIRA to the whole world.
Instead open a single entry in the firewall that allows only communication to a specific URL, since iHUB supports custom URLs we recommend to use a UUID to make it even more secure.
Here is an example.
On your Firewall open up <baseurl>/rest/restfulintegrator/1.0/incoming/014aed18-c4d2-4166-9745-39648cce64e9 (we have used https://www.uuidgenerator.net/ to generate the UUID)
Then on iHUB Incoming rule use this as a URL Condition which says
- Operand ~ (contains)
- Value 014aed18-c4d2-4166-9745-39648cce64e9