LATE state in the Task flow?

[sabina volpicelli]

Is it a good idea to have a LATE state in the Task workflow or are there better way to monitor late tasks?

[Kristján Geir Mathiesen · Accepted solution]

Hi @sabina volpicelli and...

Personally, I like to use a custom field for that kind of status since an Issue can be late (or at risk or behind) and still be in the status "In Progress". Therefore, I like to be able to have both of this information independent of each other. I usually create a single select field, which can be updated. Sometimes I make looped transitions and have a transition screen with this field on it (along with other fields we want to have updated). Sometimes I've named this transition "Update".

HTH,
KGM

[sabina volpicelli]

Thank you very much for your suggestion, I will try this way.

C

Saby

[Kelly Arrey · Accepted solution]

Hi @sabina volpicelli,

As @Kristján Geir Mathiesen has said, I would recommend against making Late a status. In addition to his suggestion of a custom field, you could:

• you could use JCL in a filter or swimlane to identify late issues, e.g., `status not in (Done, Closed) and "Due Date" < -7d`
• you could set up an automation rule based on a scheduled trigger that would run every day, and set a label like "Late" for any issues that match the above JCL. You might want to add a second rule to remove the label when the issue is Done or Closed.

HTH, 

Kel

[sabina volpicelli]

Thank You for this further insight: I have a lot to learn.

Saby