feat: jira supports timefilter by updated_at#4408
Merged
Merged
Conversation
likyh
reviewed
Feb 13, 2023
likyh
reviewed
Feb 13, 2023
klesh
force-pushed
the
kw-4403-timefilter
branch
from
fc379c8 to
4ffee39
Compare
klesh
force-pushed
the
kw-4403-timefilter
branch
from
bb1c444 to
75c9083
Compare
klesh
changed the title
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
3 participants
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.
Summary
In order to address issue #4403 , the following actions were taken:
TimeAftertocollector_stateas well as jiraTaskOptionsandTaskDataApiCollectorStateManager.IsIncrementalwas modified to takeTimeAfteras the First Factor to consider, or fallback toCreatedDateAfterifTimeAfteromitted. In other words,TimeAfterwould override theCreatedDateAfteroptionissue_collectorwas modified to follow the principle accordinglyDoes this close any open issues?
Closes #4403
Screenshots
The initial collection, should respect the
timeAfteroptionWhenever an older issue got updated, it should be collected.
