Firewall Configuration for Jira Data Center (Server) Integration

~ minute read
This is available in UserVoice Discovery Premium.

Not included in your plan? Want to learn more about the benefits? Leave us a message! If you're viewing this on our Help Center, click the Support bubble in the lower-right of this page.
 
If your Jira Data Center instance is behind a firewall, you will need to work with your IT or Systems team to make sure that UserVoice can reach the endpoints listed below.
 
If you also require the UserVoice IPs to whitelist please click the Support icon in the lower-right to request them.
 
*This article is related to the Jira Data Center (Server) Integration. You can read more about the integration here. 
 

Auth routes: 
Obtain Jira request token: (POST)
/plugins/servlet/oauth/request-token
Obtain access token: (POST)
/plugins/servlet/oauth/access-token

Webhooks:
Create webhooks: (POST) - Used to create a webhook initially that listens to issue events and sends them to UserVoice.
/rest/webhooks/1.0/webhook

Check if webhooks exist: (GET)
/rest/webhooks/1.0/webhook/:webhook_id
Delete webhooks: (DELETE) - Used to delete the created webhook if you delete the integration from within UserVoice.
/rest/webhooks/1.0/webhook/:webhook_id
Custom Fields:
Create custom fields: (POST)
/rest/api/2/field

CreateMeta:
Get metadata in order to create an issue (GET)
/rest/api/2/issue/createmeta

Issues:
Create an Issue (GET) See documentation
/secure/CreateIssueDetails!init.jspa
Get an Issue and it’s Changelog (GET)
/rest/api/2/issue/:key
Update UserVoice custom field for an Issue (PUT)
/rest/api/2/issue/:key

Projects:
Get list of all Projects (GET)
/rest/api/2/project

Search:
Search for existing UserVoice custom field (GET) - Used to validate that an issue exists when a user attempts to link an issue by ID.
/rest/api/2/search

 

Related articles