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

   ### 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
   
   Several Grafana dashboard introduction panels hardcode specific data sources 
(e.g. "GitHub and Jira") even though the underlying SQL queries use generic 
domain layer tables (`pull_requests`, `issues`, `boards`) that work with any 
supported Git tool or issue tracker.
   
   Affected dashboards:
   - **EngineeringThroughputAndCycleTime.json** - says "GitHub and Jira"
   - **EngineeringThroughputAndCycleTimeTeamView.json** - says "GitHub and Jira"
   - **WeeklyBugRetro.json** - says "GitHub or Jira"
   - **EngineeringOverview.json** - says "Jira + GitHub, or Jira + GitLab" 
(better, but still incomplete)
   
   This is misleading for users of GitLab, Bitbucket, Azure DevOps, etc. who 
may think these dashboards do not support their stack.
   
   ### What you expected to happen
   
   Dashboard descriptions should list all supported data sources, consistent 
with how other dashboards (e.g. DORA, WorkLogs) already do it.
   
   ### How to reproduce
   
   Open any of the above dashboards and read the "Dashboard Introduction" panel.
   
   ### Anything else
   
   Other dashboards like DORA.json and WorkLogs.json already follow the correct 
pattern, listing multiple sources (e.g. "One of the Git tools, e.g. GitHub, 
GitLab, Bitbucket or Azure DevOps").
   
   ### Version
   
   main branch
   
   ### Are you willing to submit PR?
   
   - [X] 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