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

Where in JIRA database is field "Σ Remaining Estimate" and "Remaining Estimate" stored

Andre van Rossem_mnkifh

Hi.

I am looking inside our JIRA database (SQL server) for the location where the fields "Σ Remaining Estimate" and "Remaining Estimate" are stored.

So I am looking for the table-name and columns name.

Can someone please let me know where I can find this?

Thanks,

Andre

Accepted answers

Nic Brough -Adaptavist-

They're not stored in the database, they are calculated. You'll have to code to accumulate the values yourself, every time.

Please, do not try reporting off a Jira database, it's not designed for it and is the single worst possible way to try to do any reporting for Jira.

All comments

Nic Brough -Adaptavist-

They're not stored in the database, they are calculated. You'll have to code to accumulate the values yourself, every time.

Please, do not try reporting off a Jira database, it's not designed for it and is the single worst possible way to try to do any reporting for Jira.

Andre van Rossem_mnkifh

Hi Nic,

Thanks for your quick answer. Do you know where this value is calculated from? (wich fields are used? formula?

Nic Brough -Adaptavist-

Remaining estimate is stored, but also calculated which makes it "fun".

In a simple case, the users put in an estimate of X, then several worklogs are added, recording time as (say) y1, y2, and y3, giving a total of Y, then when you look at the issue, the "remaining estimate" is simply "X - Y".

But then it gets complex. Users can also adjust the remaining estimate directly, and the current estimate of time. If they've done that, then the estimate is adjusted in the database on the issue table as well.

So you've three columns to read on the issue table, plus all the worklogs.

The "Σ" fields are at least a bit more simple to explain, although even harder to replicate with SQL. They're the same as above, but summed up for all sub-tasks on top-level issues.

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

database