...
The renderRequest action is similar to curl in the sense that it allows you to send requests to a url - in this case, an Atlassian server url. The advantage to using renderRequest is that it does a number of things automatically under the covers including handling authentication, findReplace support, special handling variables, and can be used within CLI scripts and run actions. Each client implements some Some clients implement customization specific to the client.
...
| Table plus |
|---|
|
| Client | Parameter | Description |
|---|
| JIRA | project | - Validates project - standard error if not valid.
- Replaces @projectId@ with the project id in requestParameters.
- If request is blank, will set to standard project url: /browse/<project key>.
| | JIRA | issue | - Validates issue - standard error if not valid.
- If request is blank, will set to standard issue url: /browse/<issue key>
| | Confluence | space | - Ignored unless title is specified.
| | Confluence | title | - Ignored unless space is specified.
- Validates page exists - standard error if not valid.
- If request is blank, will set to the standard page url: /pages/viewpage.action?pageId=<contentId>
- If request is not blank, replaces @contentId@ with the content id of the page in requestParameters.
| | Bamboo | plan | - Validates plan exists - standard error if not valid.
- If request is blank, will set to standard plan url: /browse/<plan key>.
| | Bamboo | job | - Validates plan exists - standard error if not valid.
- If request is blank, will set to standard job url: /browse/<plan key>-<job key>
| | Bamboo | number | - Adds the job number to the url if plan or job has been provided.
|
- No specific parameters are currently available for Bitbucket or HipChat
- renderRequest is not currently available for Crucible and FishEye
|