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

For input string: "PT14400M" Error on Scrum Board

Tayyab Bashir

Hi,

In one of my Scrum Boards, when I go the "Reports" section, it gives the following error in a popup.

Error

For input string: "PT14400M"

Has anyone any idea why is this happening?
It is not occuring on any other boards, but on a particular board.
What causes this and how can I remove this?

Accepted answers

Tayyab Bashir

This error was caused by corrupt field values in Remaing Estimate field.
Somehow String values were passed in remaining estimate field instead of what is expected, integer values

For e.g.
Remaining etimate had PT14400M instead of 14400 value.

This was resolved by updating the fields in the database.

All comments

Nic Brough -Adaptavist-

Do you recognise that as any data that might be on an issue?

Tayyab Bashir

Do I need to check in all the issues that are in the backlog?
Or the ones in the current sprint?

Tayyab Bashir

And what exactly am I looking for?
You mean to say the error on board could be because of some data input in any of the issues?

Tayyab Bashir

Bascially the error occurs when I view the Burndown Chart, in "Remaining Time Estimate" Metric.

And if there is an issue in sprint which doesn't have a Original Time Estimate and it doesn't have any Work Logged,
But it does have "Remaining Time Estimate".
This somehow gives an error.

Im not sure why's this happening

Tayyab Bashir

This error was caused by corrupt field values in Remaing Estimate field.
Somehow String values were passed in remaining estimate field instead of what is expected, integer values

For e.g.
Remaining etimate had PT14400M instead of 14400 value.

This was resolved by updating the fields in the database.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

scrum