vincentpatella opened a new issue, #8199:
URL: https://github.com/apache/incubator-devlake/issues/8199

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   PR data is capped at 101 for one of our Projects.  We have a project that is 
pulling data from Azure DevOps to collect metrics on the repo.  One of the 
metrics, Number of New Pull Requests, always shows 101 entries for the month.  
However, it has showed this same number for the past month.  When we 
investigated it, it looks like earlier entries are being deleted or not counted 
by DevLake, capping the amount of PRs.  This is preventing us from getting 
accurate data for this repo.  We have updated our Blueprint to collect from the 
last 6 months and run 'Collect Data in Full Refresh Mode', but neither helped 
get the older data.  Is there another setting we're missing that will allow us 
to collect this data, or is this a bug within DevLake?
   
   ### What do you expect to happen
   
   We expect to see PR data from the past 6 months for our repo show up in our 
Grafana dashboard using the stock Azure DevOps dashboard.
   
   ### How to reproduce
   
   1. Set up a Project
   2. Add an Azure DevOps Data Connection
   3. Select a repo that gets lots of PRs (over 100/ month)
   4. Set the sync policy for the past 6 months
   5. Collect data
   6. Check default Azure DevOps dashboard in Grafana to see if all PRs appear
   
   ### Anything else
   
   We have tried this on two versions of DevLake, but got the same error
   
   - v1.0.1-beta8
   - v1.0.2-beta4
   
   ### Version
   
   v1.0.2-beta4
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to