Hour type changed to "Project Time" used to be "Issue Time" | Community
Skip to main content
Y
yeariana
Level 2
January 17, 2025
Question

Hour type changed to "Project Time" used to be "Issue Time"

  • January 17, 2025
  • 2 replies
  • 362 views

Hello community.  Our users are saying that some time between 12/19/24 and 12/23/24 something changed in their Time Sheets when logging against a Project,  when they are selecting Hour Type.  It used to be "Issue Time". However now its "Project Time".  

I can see in the Hour Type configuration page there are two hour types,  Issue Time and Project Time.  However I think that Issue Time is reserved for Logging Hours against Requests. 

 

What makes this more confusing. is we had re-labeled "Projects" in our Layout Template to be "Issues"  And I think maybe that carried over to re-label the Project Time Hour Type.  And maybe its not now?

However, did something change around that time that is now forcing them to use Project time?

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

2 replies

KellieGardner
Community Advisor
KellieGardnerCommunity Advisor
Community Advisor
January 20, 2025

@yeariana - I'm curious where your users are logging their time that they are prompted to "pick" an hour type. From the timesheet, a task, issue/request or project, they should default to the system related object type for hour type - even if you give a custom name.

 

Nothing changed in the Workfront world and there wasn't a release around that time. So it's possible something changed in your system but it would be helpful to know how these users are going about logging their time.

 

 

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    September 1, 2025

    @yeariana Hi there, just checking in. Were you able to get this resolved? If one of the replies above helped, even if it didn’t fully solve the issue but pointed you in the right direction, marking it as accepted can still guide others who may face a similar question. And if you discovered another way to fix it, sharing your approach would be a big help to the community. Your follow-up not only closes the loop but also ensures others benefit from your experience. Thanks again for being part of the conversation!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...