⚠️ Remove dependence on Jira CreateMeta API #407
Merged
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
On Prem Jira deployments cannot be relied upon to have the CreateMeta endpoint as it can be taxing for large instances and admins may disable it. Instead of using CreateMeta, we can query project metadata on demand through cheaper endpoints and expose this through the tracker API. The UI will now need to query /trackers/:id/projects to get a list of projects to display in the select box as the `metadata` field on the Tracker resource will no longer be present. The UI can then pass the project ID through the /trackers/:id/projects/:id2/issuetypes endpoint to get the list of IssueTypes for the project. Signed-off-by: Sam Lucidi <slucidi@redhat.com>
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
mansam
changed the title
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.
On Prem Jira deployments cannot be relied upon to have the CreateMeta endpoint as it can be taxing for large instances and admins may disable it.
Instead of using CreateMeta, we can query project metadata on demand through cheaper endpoints and expose this through the tracker API.
The UI will now need to query /trackers/:id/projects to get a list of projects to display in the select box as the
metadatafield on the Tracker resource will no longer be present. The UI can then pass the project ID through the /trackers/:id/projects/:id2/issuetypes endpoint to get the list of IssueTypes for the project.