# How to Stop Time Logging on Closed Jira Issues

> Inaccurate time logging on closed Jira issues distorts reporting and billing. Here

Source: https://www.xalt.de/en/blog/stop-time-logging-on-closed-jira-issues/

Inaccurate time logging on closed Jira issues distorts reporting and billing. Here's how to restrict time logging through Jira workflow configuration.

TEAM XALT Atlassian Platinum Partner · 10 March 2025 · 4 min

In IT project management, accurate and actionable data capture is essential to make informed decisions and manage projects efficiently. A common challenge is restricting time tracking to Jira tickets (Jira Issues) that are still in progress. If team members log time on already resolved or completed tasks, this can have serious consequences:

- **Distortion of project reporting**
- **Inflation of time tracking metrics**
- **Increased administrative effort for error correction**

These inaccuracies can not only lead to incorrect billing to customers but also negatively affect the effectiveness of resource planning. Furthermore, trust in data integrity and the accuracy of the project management system is significantly undermined.

This is how you configure your Jira workflow to prevent time tracking on closed Jira Issues.

## **The consequences of inaccurate time tracking in Jira**

### 1. Inaccurate reporting

Incorrectly logged time on completed Jira Issues distorts project reporting and makes it difficult to realistically assess project progress and team performance.

### 2. Discrepancies in invoicing

Service-based IT companies rely on precise time tracking, as erroneous entries on closed tickets can lead to incorrect invoices – either by billing too many or too few hours.

### 3. Inefficient resource utilisation

Manually reviewing and correcting erroneous time entries costs valuable time and resources that could be better used for other tasks.

## **Technical solution: Restricting time tracking in Jira for closed Issues**

With the right Jira workflow configuration, you can prevent users from logging time on closed or resolved Issues. This ensures consistent, precise time tracking and reduces errors.

### **Implementing the restriction in Jira**

The following steps help you disable time tracking for completed Jira issues:

1. Navigate to the workflow configuration in Jira
  **Jira Administration \> Issues \> Workflows** Click on **Edit**.
2. Identify the statuses that should be restricted
  Examples: *Resolved*, *Closed*, *Done*
3. Edit the workflow and add the following property to the target status:

  - **Key:** jira.permission.work.denied
    - **Value:** true
4. Publish the updated workflow
  This ensures that users can no longer log time on issues with the specified status.

## **Summary: Efficient time tracking in Jira and optimised project management**

By proactively configuring time tracking in Jira, IT teams can improve data quality, optimise reporting, and increase workflow efficiency. A well-thought-out workflow adjustment ensures that the project management system runs smoothly and the team can focus on delivering high-quality results.

Configure your Jira environment optimally to secure your team's success and ensure the integrity of project data.

Do you want to build more Jira know-how? We have put together a [Jira Admin training](https://www.xalt.de/en/jira-training/) that makes your daily work with Jira easier.

You can find more detailed information in the official Atlassian documentation: [Restrict Log Work on Specific Status](https://confluence.atlassian.com/jirakb/how-to-restrict-log-work-on-a-specific-status-834225982.html).

## Ready to fix time tracking in Jira?

We help you configure your Jira workflows so your time tracking and reporting are finally accurate.

[Talk to us](https://www.xalt.de/en/contact/)

## More articles

### [Personal AI Agents Compared: Rovo, OpenClaw, and Agent SDKs Like Claude or OpenAI](https://www.xalt.de/en/blog/personal-ai-agents-compared-rovo-openclaw-and-agent-sdks/)

Rovo, OpenClaw, or Claude/OpenAI: how personal AI agents differ in 2026 and which approach fits your team.

*Atlassian*

### [BaFin Compliance for Atlassian Cloud – What Financial Institutions Need to Know Now](https://www.xalt.de/en/blog/bafin-compliance-atlassian-cloud-migration/)

New EU FSA rules have been in effect for Atlassian Cloud in financial services since December 2024. We show what has changed and how you can migrate to the cloud in a BaFin-compliant way.

*Atlassian*

### [Atlassian Team '26 Recap: The Shift to the AI-Native Organization and the Role of the Teamwork Graph](https://www.xalt.de/en/blog/atlassian-team-26-recap-teamwork-graph/)

XALT was on the ground at Atlassian Team '26 in Anaheim. Our recap covers the Teamwork Graph, Rovo, and the new Teamwork, Service, Product, Software, and Strategy Collections – and what it means for enterprises in Germany.

*Atlassian*

---

*This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*