IBM TSRM integration throws "requires a field Ticket class" exception

Description

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Markus von Rüden May 12, 2016 at 2:35 AM

Markus von Rüden May 12, 2016 at 2:35 AM

I moved the issue to OpenNMS as it is a bug in a released version.
This allows me to set the Affected and Fix Version fields without defining them again in the HGTM project.

Ronny Trommer May 11, 2016 at 2:16 PM

I got it to work with the provided patch which is the ticket INC3618 in the staging system. I had some issues with caching the jar in Karaf which prevented it from getting loaded. It represents the default mapping without any additional configuration. From my point of view we can create a pull request against the release branch for 18.0.1. The jar file as Hotfix is attached to this issue.

Chandra Gorantla May 11, 2016 at 11:46 AM
Edited

verified with staging server, with new patch, even without setting classId, this works. Is the patch really installed ? Is there a way to check the current version of the feature

Jesse White May 11, 2016 at 7:24 AM

The "Class" field should be set when the ticket contains an attribute called "classId". Is this being set on the Ticket?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created May 10, 2016 at 12:27 PM
Updated May 12, 2016 at 2:36 AM
Resolved May 12, 2016 at 2:36 AM