Cleaner separation between ticketing implementations and generic ticket updater #1

Open
opened 4 years ago by fkr · 0 comments
fkr commented 4 years ago
Owner

Currently the upper layer (ticket updater) is actually working with the Ticket struct that comes from the ticketing implementations. Instead it should work with a generic representation, while the lower layers work with a representation that corresponds to the ticketing solution. This is important since between various service desk products (request tracker, zammad, otrs) a ticket representation differs.

Currently the upper layer (ticket updater) is actually working with the Ticket struct that comes from the ticketing implementations. Instead it should work with a generic representation, while the lower layers work with a representation that corresponds to the ticketing solution. This is important since between various service desk products (request tracker, zammad, otrs) a ticket representation differs.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fkr/rotochute#1
Loading…
There is no content yet.