Skip to content

Commit 3820ab6

Browse files
devGregAclaude
authored andcommitted
docs: add ServiceDesk Plus to the Pro Integrations tool reference
Covers both editions (on-premises technician key and cloud Zoho OAuth with the self-client walkthrough and regional token endpoints), the group-name mapping identifier, priority/status name mappings, and the SDP-specific behaviors (full content sync on update, close-on-delete, mandatory-on-closure caveat). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent 8cd4fdb commit 3820ab6

2 files changed

Lines changed: 68 additions & 0 deletions

File tree

docs/content/issue_tracking/pro_integration/integrations.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ Supported Integrations:
1313
- [Azure Devops](/issue_tracking/pro_integration/integrations/#azure-devops-boards)
1414
- [GitHub](/issue_tracking/pro_integration/integrations/#github)
1515
- [GitLab Boards](/issue_tracking/pro_integration/integrations/#gitlab)
16+
- [ServiceDesk Plus](/issue_tracking/pro_integration/integrations/#servicedesk-plus)
1617
- [ServiceNow](/issue_tracking/pro_integration/integrations/#servicenow)
1718

1819
## Opening the Integrations page
@@ -71,6 +72,7 @@ For the complete list of requirements, please open the vendor specific pages bel
7172
- [Azure Devops](/issue_tracking/pro_integration/integrations/#azure-devops-boards)
7273
- [GitHub](/issue_tracking/pro_integration/integrations/#github)
7374
- [GitLab Boards](/issue_tracking/pro_integration/integrations/#gitlab)
75+
- [ServiceDesk Plus](/issue_tracking/pro_integration/integrations/#servicedesk-plus)
7476
- ServiceNow (Coming Soon)
7577

7678
## Error Handling and Debugging

docs/content/issue_tracking/pro_integration/integrations_toolreference.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -183,3 +183,69 @@ This maps to the ServiceNow Impact field.
183183
- **Closed Mapping**: `Closed`
184184
- **False Positive Mapping**: `Resolved`
185185
- **Risk Accepted Mapping**: `Resolved`
186+
187+
## ServiceDesk Plus
188+
189+
The ManageEngine ServiceDesk Plus Integration allows you to push DefectDojo Findings and Finding Groups as ServiceDesk Plus requests, assigned to a support Group of your choice. Both the **cloud** (ServiceDesk Plus OnDemand) and **on-premises** editions are supported by the same integration - the credentials you provide determine which mode is used.
190+
191+
### Instance Setup
192+
193+
- **Label** should be the label that you want to use to identify this integration.
194+
- **Location** should be set to your ServiceDesk Plus URL: `https://sdpondemand.manageengine.com` for the cloud edition (or your regional equivalent), or your server's address for on-premises installs.
195+
196+
Then provide **one** of the two credential sets:
197+
198+
#### On-premises: Technician Key
199+
200+
- **Technician Key** should be an API key generated for a technician on your server, under **Admin > General Settings > API**. Leave the Zoho OAuth fields empty.
201+
202+
#### Cloud: Zoho OAuth
203+
204+
The cloud edition authenticates through Zoho Accounts OAuth:
205+
206+
1. Open the [Zoho API Console](https://api-console.zoho.com/) and create a **Self Client**.
207+
2. Note the **Client ID** and **Client Secret**.
208+
3. In the Self Client's "Generate Code" tab, enter the scope `SDPOnDemand.requests.ALL`, choose a duration, and generate the code.
209+
4. Exchange the code for a refresh token:
210+
211+
```
212+
curl --request POST \
213+
--url 'https://accounts.zoho.com/oauth/v2/token' \
214+
--data 'grant_type=authorization_code' \
215+
--data 'client_id={{CLIENT_ID}}' \
216+
--data 'client_secret={{CLIENT_SECRET}}' \
217+
--data 'code={{GENERATED_CODE}}'
218+
```
219+
220+
5. Enter the **Client ID**, **Client Secret**, and the returned **Refresh Token** in the instance form. If your account is hosted outside the US data center, set **Token URL** to your regional Zoho Accounts endpoint (for example `https://accounts.zoho.eu/oauth/v2/token`).
221+
222+
### Issue Tracker Mapping
223+
224+
- **Group Name** should be the name of the ServiceDesk Plus support group requests will be assigned to, exactly as it appears under **Admin > Users > Support Groups**.
225+
226+
### Severity Mapping Details
227+
228+
This maps to the ServiceDesk Plus request **Priority** field by name, using your account's priority names:
229+
230+
- **Severity Field Name**: `Priority`
231+
- **Info Mapping**: `Low`
232+
- **Low Mapping**: `Normal`
233+
- **Medium Mapping**: `Medium`
234+
- **High Mapping**: `High`
235+
- **Critical Mapping**: `High`
236+
237+
### Status Mapping Details
238+
239+
This maps to the request **Status** field by name. The defaults use the built-in statuses:
240+
241+
- **Status Field Name**: `Status`
242+
- **Active Mapping**: `Open`
243+
- **Closed Mapping**: `Closed`
244+
- **False Positive Mapping**: `Closed`
245+
- **Risk Accepted Mapping**: `On Hold`
246+
247+
A few ServiceDesk Plus-specific behaviors to be aware of:
248+
249+
- Updates sync the full request content - unlike most trackers, ServiceDesk Plus allows the subject and description to be edited after creation.
250+
- Requests are closed rather than deleted when a Finding is removed; requests already Closed or Resolved are left untouched.
251+
- If your account makes fields mandatory on closure (for example a resolution), a close pushed from DefectDojo may be rejected by those rules and will appear in the Integration errors table.

0 commit comments

Comments
 (0)