search

apache / incubator-devlake

Apache DevLake is an open-source dev data platform to ingest, analyze, and visualize the fragmented data from DevOps tools, extracting insights for engineering excellence, developer experience, and community growth.
https://devlake.apache.org/
Apache License 2.0
2.5k stars 493 forks source link

[Refactor][Time Range] Allow Sync policy Time Range to be set objectively #7677

Open mdapke-insight opened 4 days ago

mdapke-insight commented 4 days ago

What and why to refactor

Sync Policy Time Range. When we choose a time range eg- 'last 6 months' as the time range, it translates into a date and then a day or two later when we recheck it, it still shows the same date, so in a nutshell now it's more than the last 6 months.!

Describe the solution you'd like

The Time Range needs to be the same value as set during the creation sync policy. devlake should collect 'last 6 months' data only, if it is specified in the time Range and not convert it into a date that does not update so the data collected at any point in time is 'last 6 months'

Related issues

(https://github.com/apache/incubator-devlake/issues/7079)

Additional context

mdapke-insight commented 4 days ago

image Here I had set the Time Range to be 'last 6 months' and now when I open it, I see the time Range not been update to last 6 months!

d4x1 commented 3 days ago

TimeFilter in SyncPolicy is a shortcut to set the time range of this project. It will collect the whole data in the time range at the first time, then it will collect data incrementally at the next run.

Do you want to maintain the project's data up-to-date for the past six months and delete the expired data?