JIRA工单预计完成日期报表需求咨询及构建建议

Great question! I’ve tackled similar JIRA reporting needs before, so let’s break this down clearly:

Are there existing reports that match this? #

JIRA doesn’t have a built-in report that exactly hits all your requirements (sequential ticket execution by rank, custom daily hours per dev, calculated completion dates, plus remaining total hours) out of the box. The closest native options like Active Sprints or Burndown Charts focus on sprint-level progress, not individual dev queues with date calculations. But don’t worry—there are solid ways to build this with native tools, plugins, or simple automation.

Recommendations to build the report #

1. Use JIRA Native Tools + ScriptRunner (Most Convenient for Teams with Plugins) #

If your team uses the ScriptRunner plugin (super common for JIRA customization), this is the fastest path:

• First, build a precise JQL filter
  Create a filter to pull all relevant tickets (e.g., project = YOUR_PROJECT AND status NOT IN (Done, Cancelled)). Make sure it includes fields: Ticket Rank, Ticket Developer, Ticket Estimated Hours, Ticket Status.
• Add scripted custom fields
  You’ll need two key scripted fields:
  • Estimated Completion Date: Write a script that:
    1. Groups tickets by Ticket Developer
    2. Sorts each dev’s tickets by Ticket Rank (highest priority first)
    3. Calculates sequential completion dates by adding estimated hours (divided by the dev’s custom daily work hours—add a Daily Work Hours custom field for this!) and skipping weekends (use JIRA’s built-in date utilities to exclude Saturdays/Sundays).
  • Remaining Total Hours per Dev: A simpler script that sums Ticket Estimated Hours for all uncompleted tickets assigned to each dev.
• Build a dashboard
  Add a Table gadget to your dashboard, select your filter, and include the scripted fields. Group the table by Ticket Developer to get a clean view of each dev’s queue, completion dates, and total remaining work.

2. Use EazyBI (For Advanced Visualization) #

If your team has EazyBI (a popular JIRA reporting plugin), you can build this without writing raw scripts:

• Create a custom measure for Remaining Total Hours: Sum estimated hours for uncompleted tickets, grouped by developer.
• Build a calculated measure for Estimated Completion Date: Use EazyBI’s date functions to handle sequential work, custom daily hours, and weekend exclusions.
• Visualize the data with a table or timeline view to see each dev’s ticket queue and completion dates at a glance.

3. Manual + Excel/Google Sheets (No Plugins Needed) #

For small teams or one-off reports, you can do this with exports and spreadsheet formulas:

• Export your JQL filter results to CSV, then open in Excel/Google Sheets.
• Calculate remaining total hours: Use SUMIF to sum estimated hours per developer (e.g., =SUMIF(B:B, "John Doe", C:C) where B is the developer column and C is estimated hours).
• Calculate completion dates: Use the WORKDAY (Excel) or WORKDAY.INTL (Google Sheets) function to add working days, adjusted for daily hours. For example:
  • First, calculate how many working days a ticket takes: =C2/D2 (C=estimated hours, D=dev’s daily hours)
  • Then, chain these dates sequentially for each dev’s ranked tickets: =WORKDAY(previous_completion_date, days_needed) (exclude weekends automatically)
• The downside is you’ll need to re-export data periodically to keep the report up to date, but it’s a quick solution for urgent needs.

4. Custom API Integration (For Full Control) #

If your team has engineering resources, you can build a fully custom solution using JIRA’s REST API:

• Pull ticket data via the API, filtering for uncompleted tickets and including all required fields.
• Write a script (Python, JavaScript, etc.) to:
  1. Group tickets by developer and sort by rank.
  2. Calculate completion dates with support for custom daily hours and weekend exclusions.
  3. Sum remaining hours per dev.
• Generate output as a CSV, HTML report, or even push the data to an internal dashboard tool. This gives you 100% control over the logic and formatting.

内容的提问来源于stack exchange，提问作者mwex501