Open
Conversation
It was followed the documentation of `order_by` on https://docs.gitlab.com/ee/api/issues.html#list-issues
jmini
requested changes
Jul 1, 2024
Collaborator
jmini
left a comment
There was a problem hiding this comment.
relative_position is still a duplicate of RELATIVE_POSITION in the IssueOrderBy enum
This file contains hidden or 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
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.
With this "Pull request" the connector gains the power to order issues and list the issues in the specified order.
Some features were implemented in this PR, namely:
reordermethod was implemented to reorder issues in same project or groupIssueOrderByEnum, respecting the documentation on GitLab API documentation (in my case, I need to use the relative_position)getGroupIssuesusingpageanditems per page