Remove jira-ruby gem
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
This issue is part of the &16949 epic. See that epic's description for more context.
About
We want to remove the jira-ruby gem which is used by the Jira integration and importer (which uses the integration).
The work includes:
- Remove the
jira-rubygem - Write a small HTTP client to interact with the Atlassian Jira API. This could go into
lib/integrations/jira/client.rbasIntegrations::Jira::Client. - All HTTP calls to use
Gitlab::HTTP - Add any other small abstractions required to make interaction neat and maintainable, for example like building issue objects.
- Refactor
Jira::Requests::Base, the base class for requests from the Jira issue integration, to use the new custom code. - Refactoring
Integrations::Jirato use the new client - Jira import which uses the integration may not need any refactoring.
Note, we will not remove the 'atlassian-jwt' gem.
AppSec review
On every MR, the Application Security Engineer stable counterpart for Import and Integrate (see this page - @ameyadarshan at time of writing) must be asked to review. The review is not blocking, so can be conducted after the MR merges.
Edited by 🤖 GitLab Bot 🤖