@TamBo64 If you add Entry Date and User ID to the filter, then you don't want to add it as a prompt as well. What if you changed your filter to just Hour Type > Not Equal > ____ and then apply the prompts for User ID, Department ID, and Entry Date. Does that generate an error? Also, is Department ID...

@ChristinaPi4 If you started with a Task Report that filtered for Task Name > Contains > Revisions, you wouldn't have to reference text mode collections. Instead, your text mode column would just be a basic valueexpression: displayname=Actual Task Start to Job Completion valuefield=HTML valueexpress...

There is a field for Issue > Last Update Date that you could use, however, that can be triggered on a variety of actions, not just a status change, so it may not always be 100% accurate. Another way would be to create a calculated field. In this blog, example #1 provides instructions for how to crea...

It has to be done through text mode, as the only field in the standard report builder would be Resolve Project > Late Note ID. Here is the column you can add to your Issue Report to show the last update on the resolving project:valuefield=resolveProject:lastNote:noteText querysort=resolveProject:las...

@thonewton That's how it looks on my end as well, but the report results work as expected (see example below). I am seeing issues where the Planned Completion Date is not equal to Date Requested, which is the custom field in my instance.Whenever you are using text mode filters, I always recommend us...

You can create a Note Report that filters for Note > Note Text > Contains > PM Status Update and then group the results by Project Name, however, that will pull in all PM Status Updates, not necessarily just the last one. I know you mentioned you didn't want to go the route of a custom field because...

I don't believe that field is in-line editable in a view/report. If you are needing to update the Schedule Mode on several projects, in your report you can click the checkbox next to multiple projects to bulk edit.  

When comparing two fields in a filter, the system doesn't add in the DE: before the custom field name (for whatever reason). If you adjust your text mode to include that, it should work! plannedCompletionDate=FIELD:DE:Flutter Creative - Due DateplannedCompletionDate_Mod=ne 

@NelsonSoans Because issues are considered a collection of a project (1 project, multiple issues) there isn't a way to SUM these values on a project report. I'd recommend creating an issue report that filters for specific issues and then grouping the results by Project Name so you can get a total. 

To add on to what has already been mentioned, there is no way for "force" users to who have already filled out the custom form to go back and fill out the new, required fields. There will have to be some enablement and communication from you/your team to ensure this information is captured on histor...