Description - Currently, when an issue is converted to a project, for any screen captures that are added to updates in the issue, only the image data transfers to the created project, and not the image itself. Why is this feature important to you - Users must manually add the image to the project af...

@Lyndsy-Denk - I can see where this workaround would not work in your situation then. For us, we use our queue topics and also custom fields to "qualify" the kind of request (service vs problem) that is submitted, rather than using issue vs request designation.

@Lyndsy-Denk - we use only requests for our request queues, so it works great. Are you saying you use both issues and requests in your request queues? @MoniqueEvans - I wish I could claim authorship on this one, but I cannot. Found it by accident when googling workarounds. I guess it would depend on...

Hi all, I just found something via AI that works incredibly well - I've searched all over Experience League, and I don't think this has been posted yet. If it has, my apologies for the duplication. This worked very well when testing in Preview. It removes the queue topic as an option for new request...

@William--  your suggestion of a calculated field to capture the original queue topic in case it gets deleted sounds like a great workaround. One question - what would happen if the queue topic is manually change/updated? Would we, in theory, lose the "original"?

Description -  Currently, Workfront utilizes the time zone on the user's computer to determine the times and dates for tasks versus the setup time zone within Workfront for the user. It also ignores the time zone schedule of the project. We are finding issues with this in a few locations within Work...