Enhancement: Task filters for date state, start date and excluded assignees - #144
Merged
Conversation
…ignees The tasks endpoint takes three filters nothing modelled: taskFilter, startDate and the new excludeResponsiblePartyIds. DateFilter carries taskFilter as a TaskDateFilter vocabulary, with each constant documenting what it returns. StartAfter is startDate, an inclusive bound on the task's own start date with no milestone fallback. The endpoint's companion endDate is deliberately not modelled: alone it bounds the due date, which DueBefore already covers, and sent beside startDate it stops the endpoint reading either one as a bound at all, switching to a due-date window it rejects with 400 past a maximum width. So there is no start-date upper bound to pair StartAfter with. ExcludeAssigneeUserIDs drops a task any listed user is assigned to, whatever its other assignees are, and matches direct assignment only.
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
1 participant
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
The tasks endpoint takes three filters, none modelled:
taskFilter,startDateand the newexcludeResponsiblePartyIds.DateFiltercarriestaskFilteras aTaskDateFiltervocabulary, with each constant documenting what it returns.StartAfterisstartDate, an inclusive bound on the task's own start date with no milestone fallback. The endpoint's companionendDateis deliberately not modelled: alone it bounds the due date, whichDueBeforealready covers, and sent besidestartDateit stops the endpoint from reading either one as a bound at all, switching to a due-date window it rejects with 400 past a maximum width. So there is nostart-dateupper bound to pairStartAfterwith.ExcludeAssigneeUserIDsdrops a task if any listed user is assigned to it, whatever its other assignees are, and matches direct assignment only.Type of Change
Testing
go test -v ./...)Checklist