Utilizing Text Mode in Issue Report to Show DateDiff | Community
Skip to main content
E
ElaineRi
New Member
August 20, 2025
Solved

Utilizing Text Mode in Issue Report to Show DateDiff

  • August 20, 2025
  • 3 replies
  • 393 views

We are trying to create a column in text mode that shows the DateDiff between the issue entry date and the resolving project entry date. This seems like an easy feat, yet we cannot get the report to display anything once the text has been configured. This works when we implement it in a project report, but we're not able to get it to display info on the issue report.

 

How would you write this to display the DateDiff in a rounded, whole number? We've tried at least 50 different variations of text code and nothing seems to work. Is this just not possible for our use case? 

Best answer by KellieGardner

These will all have to be done through text mode, so if you aren't familiar with that it'll be a little challenging. 

 

If you are comparing a request with the resolvable project, it will always be resolving project and not just project

 

Example: For an Issue/Request Report - shows the request entry date vs the project entry date.

valueexpression=ROUND(DATEDIFF({resolveProject}.{entryDate},{entryDate})) valueformat=int displayname=Request Entry vs Project Planned Completion Date

 

 

Overview of calculated data expressions | Adobe Workfront

Text mode syntax overview | Adobe Workfront

3 replies

S
ScottMo1
Level 4
August 20, 2025

Hi Elaine - well, what I do when all else fails in trying to do a calculation is a report is to create a custom field and add it to the object.   I complete the calculation in the custom field, then display it in the report.

 

There might be a better way, but for me this reduces the hours of frustration in trying to get it to show in a report.   Plus, I can us AI to help me if the calculation in the custom field has an error.

 

Scott

Angie_S
Angie_S
Level 3
August 20, 2025

Disclosure: I am a newbie to text mode.

 

I wonder if it has to do with "resolve project entry date" not being a field that exists on the Issue object level per the API explorer. For Projects, "converted issue entry date" does exist, so from that perspective, it makes sense that this could work for your project report and not your issue report.

 

If we can only calculate date differences on the same object or on the parent of an object, this may not be possible for an issue report.

 

If we try thinking through this another way: For this use case, what purpose would the issue version of the report have that wasn't already covered by the project version of the report? Is it a visibility thing where you are already looking at a list of issues anyway so having that extra column of data would be easier than having a totally separate report? (If so, I feel ya...hate having to look multiple places for info.)

 

Is there another potential flag that could be used in place of resolve project entry date? For example in my environment, when an issue is converted to a project and the project goes into Current status, it means the corresponding issue goes into In Progress. Could you capture that timestamp (via a calculated field that you would need to create first and attach to the issue) that the issue goes from New to In Progress status change and calculate from that date?

KellieGardner
Community Advisor
KellieGardnerCommunity AdvisorAccepted solution
Community Advisor
August 20, 2025

These will all have to be done through text mode, so if you aren't familiar with that it'll be a little challenging. 

 

If you are comparing a request with the resolvable project, it will always be resolving project and not just project

 

Example: For an Issue/Request Report - shows the request entry date vs the project entry date.

valueexpression=ROUND(DATEDIFF({resolveProject}.{entryDate},{entryDate})) valueformat=int displayname=Request Entry vs Project Planned Completion Date

 

 

Overview of calculated data expressions | Adobe Workfront

Text mode syntax overview | Adobe Workfront

Terms & ConditionsAccessibility statement

Loading footer...