View all recipes

Unassigned Jira tickets over 14 days old report template

Report on and identify unassigned Jira tickets that are over 2 weeks old and in ‘Triage’ status.

How to identify stale Jira tickets that are still unassigned

With Rippling’s ‘Unassigned Jira Tickets Report’, you can report on and identify unassigned Jira tickets that are over 2 weeks old and in ‘Triage’ status.

What do you need?

Rippling HRIS

Rippling App Management

Jira

Use Recipe Template

Recipe Overview

Jira is a helpful tool for engineers when it comes to tracking bugs, issues, and other work that needs to be done—allowing them to identify and deal with issues as soon as they come up.

But when teams fall behind on the work that needs to get done, and tickets continue to pile up in their backlog, it can be difficult for teams to differentiate between what’s important and should be tackled as soon as possible, and what can wait or may in fact no longer be an issue.

With this Recipe, you’ll be able to pull data from Jira into a list of all the tickets that’s been open for more than 14 days, unassigned, and in a Triage status; and then group them by assignee, manager, team, and more. That way, it’s easier for managers to identify all the unassigned tickets in one go, and take action to reassign or close out issues as needed.

Prefer a 7-day threshold instead of 14? As with all our report Recipes, you can customize this template with additional data, filters, grouping, and more to help you answer your specific questions.

Functions that use this recipe

Companies that use this recipe

Similar Recipes