Purpose of the incoming REST calls section it take takes care of the mapping of the data from external systems to JIRA.
...
There is a powerful rule engine which that 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
| Status | ||||||
|---|---|---|---|---|---|---|
|
...
And specify what conditions needs need 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.
| Status | ||||||
|---|---|---|---|---|---|---|
|
Last The last part is executing the action, this is done in the same manner as all other actions.
...
There is no need to open up the full JIRA to the whole world.
Instead of 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.
...
- Operand ~ (contains)
- Value 014aed18-c4d2-4166-9745-39648cce64e9
Response from Incoming REST end-point
The response will always be 200 OK with application/json as response body.