nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Data quality check in Jira

Mayur Gaikwad/Tech PMO

Hi,

Over a period of time, we have created 500+ custom fields with tons of automations across different project tracks in Jira Software. Is there a way to keep tap on data quality metrics on such custom fields or automations?

Like is correct data getting stored or are all automations firing correctly and if not, what impact is it making on data points?

Comments

Fron Flower

Here are a few suggestions for keeping track of data quality and automation metrics for custom fields in Jira:

- Set up regular audits of your custom fields to spot check data accuracy and look for anomalies. You can pull reports in Jira to analyze custom field usage and data over time.

- For critical custom fields, build validations into the creation/edit forms to prevent bad data from being entered. Jira has various validators you can use.

- Monitor errors in your automation logs to see if any automations are failing or behaving unexpectedly. Set up alerts for increased errors.

- Track key metrics over time - like number of issues with a custom field populated, number of automations run, number of errors, etc. Use this to spot trends.

- Survey teams on their experience with custom fields and automations. Gather feedback on data quality or issues.

- Set SLAs for resolution time on identified data quality issues. Track how long it takes your team to investigate and fix problems.

- Consider adding data quality tests in your QA process when releasing changes that may impact custom fields or automations.

The key is taking a proactive approach to monitoring custom field data and automation performance. Leverage Jira's reporting capabilities, track key metrics, and stay on top of user feedback. This will allow you to catch any data quality issues early.

Carlos Garcia Navarro

Hi @Mayur Gaikwad/Tech PMO

I'd also recommend to check if all these fields are used or relevant. Too many custom fields can impact performance and make maintenance harder. This post has good suggestions on how to check that: https://community.atlassian.com/t5/Jira-Software-questions/How-to-get-list-of-all-fields-that-were-never-used-in-Jira/qaq-p/1827108

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software-cloud

advanced-roadmaps