Hey everyone,
I’m trying to set up a JIRA report that shows when we can expect our tickets to be finished. Here’s what I’m hoping to include:
- Ticket priority
- Who’s working on it
- How long we think it’ll take
- Current status (like in progress, waiting, done, on hold)
The main thing I want is to see a date for when each ticket should be done. It needs to factor in that:
- Devs work on one ticket at a time
- They follow the ticket order
- They stick to the time estimates
It’d be great if the report could:
- Use 8-hour workdays
- Skip weekends
- Let us adjust hours for part-time devs
If possible, showing how many hours each dev has left on their tickets would be awesome too.
Has anyone made something like this before? Any tips on how to put it together?
Thanks for any help you can give!
I’ve tackled this problem before using a combination of Jira’s native features and some custom scripting. Here’s what worked for us:
We started by setting up a custom field for ‘Estimated Completion Date’. Then, we created a post-function on our workflow transitions that automatically updates this field based on the current date, estimated time remaining, and the assignee’s capacity.
For the report itself, we used Jira’s built-in ‘Two Dimensional Filter Statistics’ gadget. We configured it to show tickets grouped by assignee, with columns for priority, status, and our custom completion date field. This gives a quick overview of who’s working on what and when it’s likely to be done.
To handle the workday calculations and part-time devs, we wrote a small script that runs nightly. It adjusts the completion dates based on weekends and individual work schedules.
One tip: make sure to regularly review and adjust your estimates. We found that team input during sprint planning really helped improve accuracy over time.
It’s not perfect, but it’s been a game-changer for our project management. Let me know if you want more details on any part of the setup!
hey sparklinggem, ive actually been working on something similar for my team. we use a custom jira plugin that calculates completion dates based on story points and velocity. it considers workdays, dev availability, and ticket priority. not perfect but gives a decent estimate. happy to share more details if ur interested!
I’ve implemented a solution for this using Jira’s ScriptRunner add-on. It allows for custom scripting to create advanced reports. By leveraging the JQL and Groovy scripting capabilities, we’ve built a report that calculates estimated completion dates based on the criteria you’ve mentioned.
The script takes into account ticket priority, assignee workload, estimated time, and current status. It uses a rolling calculation method, considering one developer’s workload at a time, and factors in weekends and custom work hours for part-time staff.
While it’s not perfect, it provides a reasonably accurate projection of ticket completion dates. The main challenge we faced was accounting for unexpected delays or changes in priority, but regular updates to the report help mitigate this issue.
If you’re interested in exploring this approach, I’d be happy to share some code snippets or discuss further implementation details.