If you look at the default Original Estimate field, it shows 0m. When you search for issues with 0m (ie originalEstimate = "0m"), issues with the default 0m will not show up in the results. However, if you overwrite the default "0m" with "0m", it will show up in the search. Does anyone have a resolution to this? It seems the UI shows "0m", but it's not actually "0m" until "0m" is manually entered into the field.
If your purpose is to be able to search for the issues where no estimate has been entered, you can use this in your JQL:
originalestimate is empty
If you want the value 0m literally plugged into the field, you will need to edit it manually, or use Automation to set it, or you may be able to find an app that would help you default the field to that value during the creation of the issue rather than using Automation to set it after the creation of the issue.
Thanks, Trudy. The reason behind this is we need assignees to confirm that the work is truly 0m. We could search for "empty", but that leaves the uncertainty that the assignee just forgot to fill out the original estimate field. Automation may be our best bet, as you suggested. I do wonder if this is the intended behavior or not, though, since the "0m" is not actually "0m".
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events