How Sandoz Improved Reporting and Progress Tracking with Issue History for Jira

About Sandoz Company

🚧 Challenge: Sandoz needed better access to Jira changelog data for reporting and progress analysis. The team had trouble tracking changes and updates. Audits took too much time, and looking into past activity required manual work.

One challenge was understanding how Jira work items changed over time. They also needed this historical context to measure actual progress over specific periods.

💡 Solution: Sandoz uses Issue History for Jira to access detailed historical changes across Jira fields and support both day-to-day reporting and internal auditing.

The team can investigate changes to dates, statuses, assignees, estimates, and other key fields without reviewing individual Jira work items one by one. Issue History data is also exported and combined with other Jira data to analyze progress over different periods and create reporting for program leads.

As the customer explained:

“Issue History gives us that additional layer... something has been changed, when it was changed, who has changed.”

The team also uses Issue History for weekly internal changelog audits of specific fields, including Fix Versions and workstream changes.

🚀 Impact: The customer identified three main improvements since adopting Issue History for Jira: Time savings in tracking changes, simplified audit and compliance processes, and enhanced reporting and insights.

Instead of manually reviewing Jira work items one by one, the team can access historical changes in a reportable format and use them to understand how work progresses over time.

Issue History also supports more detailed status-transition analysis. For example, when a work item can reach completion through several different workflow paths, the team can identify when it moved to Complete and from which previous status directly from its historical data.

Supporting Day-to-Day Reporting

Historical Jira data provides Sandoz with extra information for reporting.

The team uses Issue History to see how work progresses over time. This includes changes that happened on a specific day, week, or month.

Sandoz uses Issue History for internal audits of Jira changelog data.

The team regularly checks key fields, including Fix Versions and Work Streams. They use historical records to investigate changes.

For example, when a new value is introduced or work shifts between different Work Streams, Issue History helps the team understand what happened and who made the change.

Biswajit described this process as:

“It’s kind of a simple auditing, like who changed what, when.”

Issue History helps the team look into where and why work may be slowing down, in addition to reporting and internal auditing.

By reviewing changes over time, the team can look at status transitions and changes to key fields like target dates, assignees, and estimates. This historical context makes it easier to see how work progressed between reporting periods and spot potential bottlenecks or gaps in execution.

For example, when a work item is completed through different workflow paths, Issue History shows when the transition happened and which status the work item moved from.

Looking at historical data from various points in time also helps the team spot gaps between stages, changes in expected timelines, and times when progress may have slowed down.

This gives Sandoz more context than just the current Jira data and offers a clearer view of how work really progressed over time.

The team uses Issue History reports in Power BI. They combine historical Jira change data with broader reporting. This gives project leads more context for examining progress over days, weeks, and months. It also helps them explore potential bottlenecks affecting the current project status.

Issue History adds a historical layer to Sandoz's reporting. It shows not only where work stands now but also how long each step took, where gaps happened, what changed, and how work progressed over time.