Time Tracking Fields

If you’ve ever opened a Done  issue in Jira and seen “Time spent: 0m” , you know the pain. Reports become useless, teams forget to log work, and suddenly nobody trusts the numbers. A lot of people search for things like: “Jira require time to be logged before transition” “block Jira transition until worklog exists” “Jira workflow validator logged time” Out of the box, Jira Cloud doesn’t ship with a validator that does exactly this.That’s why we added a “Require time to be log

Jira only has one time tracking field. What if your team needs more? If you’ve ever typed something like “Jira multiple time tracking fields”, “separate Dev and QA time in Jira” or “billable vs non-billable time in Jira” into Google, you’ve already hit one of Jira’s oldest limitations: it only really understands one  time budget per issue. Out of the box you get a single Time Tracking  field with three numbers behind it: Original Estimate , Remaining Estimate  and Time Spent