Match issue types schema using project key on JIRA Server
requested to merge 324251-fetching-jira-issue-types-via-services-jira-test-returns-500-error-when-using-a-self-hosted into master
What does this MR do?
This MR changes the way we integrate with JIRA Server
On JIRA Cloud, rest/api/2/issuetypescheme/project
would give you issue type schema for the active project. But when using JIRA Server you can have multiple projects. As such, we need need to lookup the project using project key and then fetch the issue type scheme active for the given project.
Screenshots
Before
After
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because this is a bug fix.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Related to #324251 (closed)
Edited by Michał Zając