Refactor: Extract OneIssueTracker limitation
What does this MR do and why?
Extract common methods from Integrations::BaseIssueTracker
into Integrations::OneIssueTracker
.
JH Team is about to contribute a new issue tracker service: ONES
.
Issue link: #365123 (closed)
Other issue trackers inherit from Integrations::BaseIssueTracker
, it contains a lot of methods that ONES
doesn't need.
So I want to extract Integrations::OneIssueTracker
to avoid introducing useless methods in ONES
and to reuse the common methods in OneIssueTracker
.
/cc JH EM @prajnamas
Edited by Baodong