Request primary assignment entry date use for cycle time calculations | Community
Skip to main content
C
CBuckwal
Level 4
January 3, 2025
Solved

Request primary assignment entry date use for cycle time calculations

  • January 3, 2025
  • 2 replies
  • 939 views

I've been asked to create a request report that captures the time from the request entry date to the first user assignment date. Will the primary assignment entry date reliably return that date? My initial testing looks like this is a valid field for what I want to calculate, but I wanted to double check here. 

I've reviewed the Tips and Tricks Calculated Fields https://experienceleague.adobe.com/en/docs/events/the-skill-exchange-recordings/workfront/apr2022/calculated-fields, and thought I could use the SLA section (around 8:15) in the video to create the entry date-first assignment calculation. But the video shows "User First Assigned" in the calculation and I'm not sure where that field comes from, since it's not a database field and if it's a calculated field, I missed how the field was created. 

Thanks for any insights on this.

Cathy

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by NicholeVargas

The field in the video, User First Assigned, was a calculated custom field so if you want to follow the same format, what you'll do is:

  • Go to your request custom form 
  • Add a new calculated custom field (Format = Date). Click Apply. This will create your field in the database. 
  • Go back to edit this custom field and add the calculation:
    IF(ISBLANK({assignedToID}),{DE:User First Assigned},IF(ISBLANK({DE:User First Assigned}),$$NOW,{DE:User First Assigned}))

NOTE:This will capture the date in which the request was first assigned to an individual, not a team. 

  • Save and Close. 
  • Keep in mind that this will only work for new issues moving forward, as it will capture the date and time of the assignment. It won't historically populate past requests.

Once you have your User First Assigned custom field created, create a second calculated custom field to count the number of days between the request entry date and the date the request was first assigned. 

  • Go to your request custom form
  • Create a new calculated custom field (Format = Number)
  • Add the following calculation: ROUND(DATEDIFF({DE:User First Assigned},{entryDate}),2)
  • Save and Close.
Hope that helps! 

2 replies

C
CBuckwalAuthor
Level 4
January 3, 2025

Looking into this further, I find that I can't use the primary assignment entry date in a calculated field without a class casting error. I found the primary assignment entry date in an issue report, so I thought it could be used in a calculated field. The text mode for the issue primary assignment entry date field is below. Looking through the API Explorer got me more confused, since I couldn't find primaryAssignment:entryDate

displayname=
linkedname=primaryAssignment
namekey=view.relatedcolumn
namekeyargkey.0=primaryAssignment
namekeyargkey.1=entryDate
valuefield=primaryAssignment:entryDate
valueformat=atDate
 

I tried the following expression and received the class casting error.  

ROUND(WORKMINUTESDIFF({entryDate},{primaryAssignment}.{entryDate})/480,0)
Kurt_Jones
Community Advisor
Kurt_JonesCommunity Advisor
Community Advisor
January 6, 2025

CBuckwal,  it looks like you're trying to get the number of days between when the request was entered and when someone got assigned.  Have you tried ROUND(DATEDIFF({entryDate,{primaryAssignment}.{entryDate}),0)?  DATEDIFF will give you the days between two different dates.

C
CBuckwalAuthor
Level 4
January 6, 2025

Thanks, Kurt. I tried your suggestion and receive the same error when I try to save:

The following fields are invalid: class com.attask.persist.mapping.query.RKOneToOneQueryKey cannot be cast to class org.eclipse.persistence.mappings.DatabaseMapping (com.attask.persist.mapping.query.RKOneToOneQueryKey is in unnamed module of loader 'deployment.redrock.ear.java.jar' @5d146f42; org.eclipse.persistence.mappings.DatabaseMapping is in unnamed module of loader 'deployment.redrock.ear' @1c74c7c2) Invalid Expression: class com.attask.persist.mapping.query.RKOneToOneQueryKey cannot be cast to class org.eclipse.persistence.mappings.DatabaseMapping (com.attask.persist.mapping.query.RKOneToOneQueryKey is in unnamed module of loader 'deployment.redrock.ear.java.jar' @5d146f42; org.eclipse.persistence.mappings.DatabaseMapping is in unnamed module of loader 'deployment.redrock.ear' @1c74c7c2)

 

I think it's the primary assignment field, which works as a report column, but doesn't seem to work in a calculated expression. 

NicholeVargas
Adobe Employee
NicholeVargasAdobe EmployeeAccepted solution
Adobe Employee
January 8, 2025

The field in the video, User First Assigned, was a calculated custom field so if you want to follow the same format, what you'll do is:

  • Go to your request custom form 
  • Add a new calculated custom field (Format = Date). Click Apply. This will create your field in the database. 
  • Go back to edit this custom field and add the calculation:
    IF(ISBLANK({assignedToID}),{DE:User First Assigned},IF(ISBLANK({DE:User First Assigned}),$$NOW,{DE:User First Assigned}))

NOTE:This will capture the date in which the request was first assigned to an individual, not a team. 

  • Save and Close. 
  • Keep in mind that this will only work for new issues moving forward, as it will capture the date and time of the assignment. It won't historically populate past requests.

Once you have your User First Assigned custom field created, create a second calculated custom field to count the number of days between the request entry date and the date the request was first assigned. 

  • Go to your request custom form
  • Create a new calculated custom field (Format = Number)
  • Add the following calculation: ROUND(DATEDIFF({DE:User First Assigned},{entryDate}),2)
  • Save and Close.
Hope that helps! 
C
CBuckwalAuthor
Level 4
January 9, 2025

Thanks very much, Nicole. I was able to create the fields using your instructions and it works well. Part of my confusion in the beginning was that I forgot to add the field prefix my team uses to the calculation, so I kept getting errors. 

I understand $$NOW is going to prohibit using this calculation historically. Is there another option to get the same information for older assigned requests?

I tried the following expression using {entryDate},{primaryAssignment} found in project report columns in the calculated field and received a class casting error due to {entryDate},{primaryAssignment} I think. 

ROUND(WORKMINUTESDIFF({entryDate},{primaryAssignment}.{entryDate})/480,0) 
Why does {entryDate},{primaryAssignment} show as a project report column option but isn't usable in a calculated field?
Terms & ConditionsAccessibility statement

Loading footer...