一款真正的 AI 报表诞生了！JimuChatBI —— 首款免费开源对话式智能数据分析产品（Chat2BI）。 一句话生成报表和数据大屏，支持对话式 AI 修改优化；类 Excel 在线报表设计，兼容国产信创数据源。 对着 AI 说句话，报表就出来了——表格、图表、分组汇总自动生成，复杂报表场景轻松应对。想做数据大屏？同样一句话搞定，让数据分析进入 AI 时代。
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
jeecgboot/jimureport has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jeecgboot/jimureport respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 7.5 places jeecgboot/jimureport in the D tier.
The external contributor pull request merge rate for jeecgboot/jimureport is 0.0%, based on public PR activity from non-core contributors.
jeecgboot/jimureport currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in jeecgboot/jimureport welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/jeecgboot/jimureport?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
版本号：2.3.4版本 问题描述：打印当前页的打印效率有点低，请求加上拉起浏览器打印页就3秒多了 错误日志&截图： 20260922_171717.mp4 重现步骤：点击默认打印、打印当前页 友情提示（为了提高issue处理效率）： 积木报表是一款免费报表产品，功能免费源码不开放; 未按格式要求发帖，会被直接删掉; 请针对问题提供[报表设计配置或SQL脚本]或在官网制作报表示例并提供ID; 针对不好重现的问题，请录制操作视频或详细的重现步骤；
版本号： 2.1.5 分支： 问题描述： 积木报表设置两级横向分组，一级分组标题无法设置分组合计 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
版本号：3.9.5 分支： 问题描述： 积木报表在线填报表单中数据字典不能获取系统中已有数据字典、新增又提示编码已经存在 1、静态数据源：只支持选项（只有显示文本，没有值），应该增加文本值，同时增加json灵活配置（不需要一行行手动添加效率更高）； 2、数据字典：建议可以从系统数据字典中获取、只能编辑积木报表中新增的字典、系统字典可以只给调用权限； 3、API字典：系统管理中的字典API需要Token，此处不能调用； 4、表字典：表字典只能选择表，选择了数据字典表后无法通过SQL过滤，是不是加个过滤功能或自定义SQL（类似数据集）； 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
版本号： 2.5.3 问题描述： 如果想做到报表里面显示的图片是安全的。。 因为图片在OSS 里面设置了 refrence 限制。。那么在报表里面就显示不出来这个图片。因为会 403 拒绝访问。这个情况应怎么处理呢。 错误日志&截图： 2026-09-17 19:49:33.366 [http-nio-8080-exec-16] ERROR o.jeecg.common.exception.JeecgBootExceptionHandler:141 - 403 Forbidden on GET request for "https://yundtai-boot.oss-cn-hangzhou.aliyuncs.com/prod/upload6aa9f470e4b0b63f8754c23b.jpg": " AccessDenied You are denied by bucket referer policy. 6AABD3CD749FDB3431ADD1FF yundtai-boot.oss-cn-hangzhou.aliyuncs.com yundtai-boot 0003-00000501 https://api.aliyun.com/troubleshoot?q=0003-00000501" org.springframework.web.client.HttpClientErrorException WrappingRunnable.run(TaskThread.java:57)atjava.base/java.lang.Thread.run(UnknownSource)2026−09−1719:49:33.367[http−nio−8080−exec−2]ERRORo.jeecg.common.exception.JeecgBootExceptionHandler:141−403Forb
版本号：2.5.0 问题描述：多行填报下按钮需设置开启/禁用功能 错误日志&截图： 重现步骤： 友情提示（为了提高issue处理效率）： 积木报表是一款免费报表产品，功能免费源码不开放; 未按格式要求发帖，会被直接删掉; 请针对问题提供[报表设计配置或SQL脚本]或在官网制作报表示例并提供ID; 针对不好重现的问题，请录制操作视频或详细的重现步骤；
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to jeecgboot/jimureport, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of jeecgboot/jimureport acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
jeecgboot/jimureport has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 7.5 places jeecgboot/jimureport in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jeecgboot/jimureport currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jeecgboot/jimureport are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.