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

Associating the burndown chart vertical axis with a custom field

Andy Nash_h4pgmz

I created a custom field for story estimation

I want to use the standard burndown chart to display progress against this field.

But I cannot get the field to display as one of the optional fields to chose from in the drop down list.

Any help appreciated!

Accepted answers

Ignacio Pulgar

The custom field must be numeric in order to use it in the report. Is that the case?

shetty

hi andy

yes the custom field should be numeric field then you will get your required field in dropdown list

All comments

Ignacio Pulgar

The custom field must be numeric in order to use it in the report. Is that the case?

shetty

hi andy

yes the custom field should be numeric field then you will get your required field in dropdown list

Andy Nash_h4pgmz

Yeah it is. Fibonacci scale.

But ahhh, it's not classed as a Numeric field, but as a Select list (Single choice).

Guessing that's what's tripping things up.

Jira is so restrictive in this respect. Grrrrr.

Ignacio Pulgar

That's why, yup.

Ignacio Pulgar

If you count with ScriptRunner, you can copy the selected value in your single select custom field to a new numeric custom field with a similar name, by transforming the string into a number.

Andy Nash_h4pgmz

Dev team! Someone call my dev team!!

Many thanks Ignacio. I'll see what we can do.

Andy Nash_h4pgmz

I switched field types to now use a Numerical field.

This is great, it enables the tracking I was looking for.

But now I've configured the Backlog view as intended, I have stumbled across another problem that I'm hoping is a mis-configuration somewhere (but having searched every setting I can think of, have come up short).

Ignacio Pulgar

Hi again Andy,

Those three numbers are the sum of the SPs of issues as per the following definitions:

First: Issues in a status mapped to the left-most column.

Second: Issues in a status mapped to any columns other than the left-most or the right-most ones.

Third: Issues mapped to the right-most column.

That said, you should use the right-most column for issues that are already Done, and move the Not Required ones to a different place.

Andy Nash_h4pgmz

Brilliant - I love JIRA more and more each day!

I'm guessing that's a 'Feature' rather than a bug ;-)

Many many thanks - dunno how I would have worked that out myself.

Muchisimas gracias!

Ignacio Pulgar

De nada!

Yes, that's a convenient feature and something to have in mind for all Jira Software specific reports (those based in boards) where the presence of a resolution doesn't necessarily mean that the issue can be considered as Done.

Best regards!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud