-
-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Issue Board List by Milestone #519
Comments
I would change it to remove the label_id as a required argument, and just pass it in the options like you suggested. Then release it as a breaking change so users will not be caught off guard if their latest update doesnt work the same way. The change will be documented in the changelog :) |
Was fixing this one up and noticed a small inconsistency. The group issue board docs do not mention milestoneId being a property? https://docs.gitlab.com/ee/api/group_boards.html#new-group-issue-board-list |
Can anyone verify this to make sure i'm not missing something? |
You are not missing anything but the docs are. I don't have a reduced test case I can lay out but I have this:
And it's working with the API to create a list inside my existing board that is defined by a milestone. |
Ill bring it up with Gitlab as well! |
Which version of Gitlab are you using? |
That script runs weekly and last time it ran we were on 12.9. We're on 12.10 now and it'll run tomorrow night so I can confirm it still works there if needed. |
Perfect, ill connect the issues as well! Thank you !! |
Still awaiting the response from Gitlab on the proper way forward. |
Description
I am trying to automate the management of some milestone-based GitLab boards and found a situation where I need to create a list based on the
milestone_id
and not thelabel_id
but the current implementation: https://github.com/jdalrymple/gitbeaker/blob/master/src/core/templates/ResourceIssueBoards.ts#L26 doesn't allow me to leave off thelabel_id
. The GitLab API won't allow both to be passed and I don't want both to be passed.Steps to reproduce
Call
GroupIssueBoards.createList( groupId, boardId, null, { milestoneId: 123 } )
Expected behaviour
I can specify just the
milestone_id
and it'll work. I have this working using rawgot
calls but that's not so ideal.Actual behaviour
The GitLab API will throw an error saying
label_id
andmilestone_id
are mutually exclusive.Possible fixes
I think probably the easiest solution is to move the
label_id
into the options object but worried that'll be hard for users of the library to know to change. Not sure of a better way to get that same functionality without causing some gross workaround stuff. I'm happy to work on the change, just wanting to get some ideas/feedback before I start on anything.The text was updated successfully, but these errors were encountered: