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; } } }

Why is Original Estimate displaying "p" instead of hours ("h")?

Larissa Redivo dos Santos

Hi everyone,

I noticed something strange this week regarding the Original Estimate field and wanted to check if anyone else is experiencing the same behavior.

When I open a task, the original estimate time that used to be displayed in hours (e.g., "h") is now showing as "p". However, when I view the same task on the board, the estimate still appears correctly in hours ("h").

This inconsistency makes me think it might be a bug, but I haven’t found any related reports yet.

Has anyone else encountered this issue or knows what might be causing it?

My Jira is in Portuguese, where:

"Estimativa original" = "Original Estimate"

Screenshots:

1. Task view → showing "p" (incorrect)

Captura de tela 2026-04-24 152741.png

2. Board view → showing "h" (expected behavior)

Captura de tela 2026-04-24 152953d.png

Thanks in advance!

Accepted answers

Bill Sheboy

Hi @Larissa Redivo dos Santos

There is an open defect for this symptom in the JAC backlog:

https://jira.atlassian.com/browse/JRACLOUD-98161

And, there are several other open defects for other languages related to incorrect translations for time tracking fields.

Kind regards,
Bill

All comments

John Funk

Hi Larissa,

Looks like it's probably P for Points as in Story Points.

Larissa Redivo dos Santos

Hi John, thanks for your reply!

That was my first thought as well, but what seems odd to me is the behavior of the field itself.

When I edit the Original Estimate, it only allows time units like: w (week), d (day), h (hours), m (minutes). It doesn’t accept "p" as a valid unit. However, after I save and the issue reloads, the value that was in hours ("h") is displayed as "p".

Also, there is a separate field specifically for Story Points, which makes this even more confusing. Because of that, it doesn’t seem like an intentional "points" representation, but possibly a display issue.

John Funk

That's very weird. Can you share some screenshots where you set what unit each of those fields uses?

Trudy P Claspill

Chiming in with generic information and screens from my own system...

"Original Estimate" is a System field.

Screenshot 2026-04-24 at 12.36.00 PM.png

It is an example of a "duration" field and the format for it is set by global Time Tracking settings.

Screenshot 2026-04-24 at 12.37.45 PM.png

Bill Sheboy

Hi @Larissa Redivo dos Santos

There is an open defect for this symptom in the JAC backlog:

https://jira.atlassian.com/browse/JRACLOUD-98161

And, there are several other open defects for other languages related to incorrect translations for time tracking fields.

Kind regards,
Bill

marcos bruno nogueira miranda

The issue is set as fixed, but it's happening here. @Larissa Redivo dos Santos
Is it fixed for you?

Larissa Redivo dos Santos

Hi, @marcos bruno nogueira miranda I’m following the issue, but unfortunately it’s still happening here as well. Do you know how to report it?

marcos bruno nogueira miranda

I included a comment there. And created a new issue for the translation team
https://jira.atlassian.com/browse/I18N-4599

You can create an issue here

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

original-estimate