Breadcrumbs

Timely resolution assessment

📚

This template displays the assessment of whether the resolution was set before the due data.

If it was set on time, “Yes” will be displayed and if it was not, “No” will be displayed.

If there is no due date or it was not reached yet, “None” will be displayed.

Configuration

To use the Timely resolution assessment template, simply select it from the template grid. Filter by Misc to find it faster.

Parameters

This template does not require any additional parameter configuration.

Expert mode

If you switch to Expert mode you can see the formula field in the Expression Parser. You can now tweak the expression to create a custom formula field based on this template.

Expression

General expression:

%{{issue.resolutionDate} != null AND {issue.dueDate} != null
? ({issue.resolutionDate} <= {issue.dueDate} ? "Yes" : "No")
: (datePart({system.currentDateTime}, RUN_AS_LOCAL) > {issue.dueDate} ? "No" : "")}

Used parser functions

The links lead to the JWTC documentation because the parser functions are shared functionalities.

Details

1. What does the expression do?

This expression checks if a work item was resolved before its due date. It returns:

  • "Yes" if the resolution was set on or before the due date,

  • "No" if it was set after the due date,

  • "None" if there is no due date or the due date hasn't been reached yet.

2. Step-by-step breakdown

Here is the expression:

%{{issue.resolutionDate} != null AND {issue.dueDate} != null
? ({issue.resolutionDate} <= {issue.dueDate} ? "Yes" : "No")
: (datePart({system.currentDateTime}, RUN_AS_LOCAL) > {issue.dueDate} ? "No" : "")}

Let's break it down:

  • {issue.resolutionDate} != null AND {issue.dueDate} != null

    • Checks if both the resolution date and due date are set for the work item.

  • If both dates are set:

    • {issue.resolutionDate} <= {issue.dueDate} ? "Yes" : "No"

      • If the resolution date is on or before the due date, return "Yes".

      • Otherwise, return "No".

  • If either date is missing:

    • datePart({system.currentDateTime}, RUN_AS_LOCAL) > {issue.dueDate} ? "No" : ""

      • Checks if the current date is past the due date.

      • If so, return "No" (meaning the work item is overdue and not resolved).

      • Otherwise, return an empty string (""), which is displayed as "None" in the field.

Technical terms explained:

  • null: Means here that the field is empty or not set.

  • datePart(): A function that extracts the date part from a date-time value, used here to compare the current date to the due date.

  • ? : (ternary operator): A shorthand way to say "if this is true, do X; otherwise, do Y".

3. Examples

  • Example 1: Work item has a due date of Feb 10, 2026, and was resolved on Feb 9, 2026.

    • Both dates are set, and resolution is before due date → returns "Yes".

  • Example 2: Work item has a due date of Feb 10, 2026, and was resolved on Feb 12, 2026.

    • Both dates are set, but resolution is after due date → returns "No".

  • Example 3: Work item has no due date.

    • Due date is missing → displays "None".

  • Example 4: Work item has a due date in the future and is not resolved yet.

    • Resolution date is missing, current date is before due date → displays "None".

  • Example 5: Work item has a due date in the past and is not resolved yet.

    • Resolution date is missing, current date is after due date → returns "No".

4. Real-life use cases

  • Project tracking: Quickly see if tasks or work items are being completed on time.

  • Team performance: Assess how often your team resolves work items before deadlines.

  • Reporting: Use this field in dashboards or reports to highlight overdue or timely resolutions.

  • Process improvement: Identify bottlenecks or recurring delays in your workflow.