Add a replacement API for jira interaction #3829
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Conflicts |
TheMeinerLP
force-pushed
the
feature/jira-api
branch
from
1d2e5bf to
cfcaea4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Issue: #3028
The following PR replaces the current Groovy file and builds a new API based on given requirements. This API is hardened and enables better maintenance on the RPU later on. In addition, the JIRA will be updated.
The new API consists of an interface and a singleton instance. In general, the singleton instance can only be called via the interface. This type of structure is intended to harden the API and make it simpler.
All current scripts already use the new API in this PR.