Enhancement of Days in Column feature criteria to include Assignee
Asked by Ron Rodrigo:

Hi I would like to make a feature enhancement request per below for the currently existing 'Days in column' Jira issue card feature:

Days in column feature (dots in cards) <https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Customizingcards-UsingDaysincolumn>  

For this feature, I would like to enhance the criteria used to determine the number of dots shown on the issue (Story and Bug) cards in our Jira Kanban board. This criteria enhancement would include BOTH:

1- days in Column/Status

AND

2- assignee  

Currently, this feature's criteria is based only on 'Days in Column (Status)'.  

Use case 1:

Tom is assigned story issue MYPROJECT-234 on June 1 which is in 'Ready for Dev' status  
1a) on June 1, Tom moves the issue status from 'Ready for Dev' to 'In Dev'  
1b) on June 8, the issue is still assigned to Tom and 'In Dev' status. There are 2 red dots showing on the issue card in the Jira Kanban board (current feature behavior).  
1c) on June 9, Tom assigns MYPROJECT-234 to Larry and remains in 'In Dev' status. As a result, no dots show up on the issue card since this is now a new assignee.  
1d) on June 10, MYPROJECT-234 would now show up with one light grey dot on the issue card since it's been in the column for 1 day with Larry as the assignee  
1e) on June 15, MYPROJECT-234 would now show up with one red dot on the issue card since it's been in the column for 5 days with Larry as the assignee

<br />

Use case 2:

Perform all the steps in Use case 1:  

2a) on June 16, Larry re-assigns MYPROJECT-234 back to Tom with issue status 'In Dev'. Immediately, the issue card on the board would show two red dots since historically, the issue has been assigned to Tom with a status of 'In Dev' for 8 days.


Answers:
author: Hannes Obweger - JXL for Jira
body: Hi [@Ron Rodrigo](/t5/user/viewprofilepage/user-id/5519660)

I understand that you want to see this information in a Kanban board. The only thing I can think of is to calculate the relevant information using Jira Automation, and write the result into a custom field. You may then be able to add the custom field to your cards, and/or write a JQL statement that selects the relevant issues in the Kanban board's card coloring feature (see [here](https://support.atlassian.com/jira-software-cloud/docs/customize-cards/)). [This article](https://confluence.atlassian.com/jirakb/how-to-use-automation-to-get-the-time-an-issue-was-in-a-status-1167838219.html) may be a good starting point for setting up your automation rules.

Alternatively, if you're open to solutions from the Atlassian Marketplace, you'll have more options. I'll add more information below.

Hope this helps,

Best,

Hannes

comments: author: Hannes Obweger - JXL for Jira
body: ... and just to expand on my last point: If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2725594).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you'd do in e.g. Excel or Google Sheets. It also comes with a number of so-called *history columns* that aren't natively available, including *time in \[status\] with \[assignee\]*, and many more.

These history columns can then be used across JXL's advanced features such as *conditional formatting*, like so:

![time-in-status-with-assignee-conditional-formatting.gif](https://community.atlassian.com/t5/image/serverpage/image-id/330849iE8A683EEF36C3EAD/image-size/large?v=v2&px=999 "time-in-status-with-assignee-conditional-formatting.gif")

(I don't have great sample data here, but you can configure the conditional formatting rules to whatever time ranges you want to highlight.)

I understand that this wouldn't be directly in the Kanban board, but perhaps might still be worth a try. This all *just works* , so there's no scripting or automation whatsoever required. I should also add that JXL can do much more than the above: From support for configurable *issue hierarchies* , to *issue grouping* by any issue field(s), *sum-ups* , or *bulk editing* via copy/paste.

Any questions just let me know!


author: Bill Sheboy
body: Hi [@Ron Rodrigo](/t5/user/viewprofilepage/user-id/5519660) -- Welcome to the Atlassian Community!

To suggest a new feature, please use this page or one of the feedback mechanisms built into Jira: <https://jira.atlassian.com/secure/Dashboard.jspa>

In the meantime, I am curious: what problem are you trying to solve? Specifically, why measure different time-in-status values for different people *but within the same status*?

I wonder if that is a symptom there are other process steps which are not reflected in the board columns and status values, or there are knowledge silos in the team leading to delays through extra handoffs between people.

Kind regards,  
Bill

comments: author: Ron Rodrigo
body: Hi Bill. We want to include the criteria of per assignee so that it gives time for a new assignee (if issue was re-assinged) to work on the issue before the issue gets stale (i.e. start seeing red dots). We want to capitalize on the existing Days in Column (dots on issue card) feature since it gives us a quick discernible way to visually see this our Kanban board. When we start seeing 1-2 red dots, this allows us to give more focus on that particular issue so we can discuss how we can move that issue to the next status in our workflow. Obviously with Kanban, the goal here is to move tickets from To Do to Done as quickly as possible.

Thank you...Ron


author: Amay Purohit_RVS
body: Hi [@Ron Rodrigo](/t5/user/viewprofilepage/user-id/5519660)

Welcome to the community !!

A mktplace app can help here. If you are open to try out one, do take a look at

[Time in Status Reports](https://marketplace.atlassian.com/apps/1226187/time-in-status-reports?hosting=cloud&tab=overview)  
Not exactly as per your use case , but one of the many reports which the app provides is Time with Assignee in hours/days to determine , how much time the issue spent with each assignee in the complete lifecycle of the issue. As you can see in the screen grab below. The other report gives more details like time with assignee per status.

The app has 20+ reports to meet a variety of time in status use cases.

[More Details here](https://community.atlassian.com/t5/App-Central/Time-in-Status-Reports/ba-p/2348133)

Disclaimer : I work for the vendor who built this app

![TWA.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/329773i1D125B0F61ABCF1C/image-size/large?v=v2&px=999 "TWA.PNG")

![TWA per Status.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/329774iCD9277D4D905064E/image-size/large?v=v2&px=999 "TWA per Status.PNG")

comments: author: Ron Rodrigo
body: Thanks Amay. Unfortunately, this solution won't work well for our engineering team b/c we want some quick discernible way to visually see on our Kanban board if an issue has been in one particular status for too long. The goal here is to move tickets from To Do to Done as quickly as possible.


Tags: cloud

jira-cloud