Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I would like to understand exactly how this is collecting data. I have some stories that don't make sense as to how many days Jira is saying are in a column. Also, I would like to know what each of the dots represent from a timeline perspective. How many days for a dot to turn gray? How many days for a dot to turn orange? How many days for a dot to turn red? How many days until a second dot shows up?
Hi @Rich Evers
The days in column feature uses the issue history data, and you may learn the specifics about what is displayed here:
https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Using-Days-in-column
Kind regards,
Bill
@Bill Sheboy I don't find this entirely true. I had a Story issuetype that rolled from one Sprint on to the next (staying in the same column), and seemed to have reset. We also have had Story issuetypes that have rolled on to the next Sprint and did not reset. Any ideas about this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is interesting...During that time, did anything change for the scrum board for status mapping to columns, add/edit/delete of status values, or to the workflow? I would expect that some of those could reset the value, while no changes would lead to carry-over values from prior sprints.
For myself and the teams I coach, we only glance at the built-in days in column value. Instead we use an Age Of WIP (custom field) that we set with an automation rule to reflect the working days in progress total, regardless of board columns.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing changed that you referenced.
Thanks for the tip on the custom field. Unfortunately due to the complexity of our org, that wouldn't work too well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Given the inconsistencies you are observing, I suggest submitting a support ticket for Atlassian to take a look. As the site admin for a paid license you should be able to do that here: https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.