Jira Tickets Data Quality Check

[ajay rajput]

I want to build a solution to track all the Jira tickets(Epics, Features, everything) that are missing relevant fields inputs like (Acceptance Criteria, Exec Summary, Labels etc).

After getting the list of tickets that needs attention, I wanna send individual comms to assignees/reporters to fill out the details.

If suppose a reporter has three tickets under his name, then a single comm with the concerned fields shall be communicated to him.

Is there a way to build this?

[Trudy P Claspill]

Hello @ajay rajput 

If the fields are relevant and important have you considered making them required so that they can't be left empty?

[Viswanathan Ramachandran]

hi @ajay rajput 

Good thought. Yes, this is achievable.

A practical approach is to treat it as a data quality/compliance process rather than just a reporting exercise.

Step 1: Identify incomplete issues

Create one or more JQL filters that identify issues with missing mandatory fields. For example:

• Description is EMPTY
• Components is EMPTY

You can combine these into a single filter (or several filters depending on your governance model) to capture all Epics, Features, Stories, Tasks, Bugs, etc.

Step 2: Aggregate by assignee or reporter

Instead of sending one notification per issue, group the results by Assignee (or Reporter if that’s your ownership model). This provides each user with a single summary listing all their issues requiring attention.

Step 3: Automate the communication

There are several ways to do this:

• Jira Automation (suitable for smaller environments)
• ScriptRunner (great for Data Center and advanced logic)
• A scheduled Python using the Jira REST API endpoints

The process would typically:

1. Run on a schedule weekly better
2. Execute the JQL.
3. Group issues by Assignee or Reporter.
4. Generate a consolidated email or Teams message.
5. Include direct links to each issue and identify which fields are missing.

Step 4: Governance reporting

In addition to notifying users, I’d recommend maintaining a dashboard showing:

• Number of incomplete issues by project
• Most frequently missing fields
• Trends over time
• Age of non-compliant issues

This helps project managers and governance teams monitor data quality instead of relying solely on individual reminders.

regards

[Gor Greyan]

Hi @ajay rajput

Welcome to the Atlassian Community!

I would approach it in two phases.

First, define the data quality rules that every issue should meet (the criterias that you mentioned). You can then use JQL and Jira Automation, or a ScriptRunner to periodically identify issues that don't satisfy those rules.

Once you have the list, you can iterate through the results and group the issues by the Reporter or Assignee. For example, if one reporter owns three issues with missing information, you can compile those three issue keys into a single message or email instead of sending three separate notifications. The same approach can be used for assignees.

Depending on your environment, this can be implemented using a scheduled Jira Automation rule or a ScriptRunner scheduled job.