@lgaertner is correct. There are many ways to enhance this as well. You can truncate the update so it doesn't create a super long column in your report, you can add the time and date of the post, the author, and even a "more..." link to reply to the update. It can be as simple or elaborate as you wi...

Adobe thinks they know better than you, who should be able to share a project. I've complained about this before to deaf ears. This goes back to the topic of system governance and how Adobe is eroding the ability of companies to govern their own instances.

I need to pull a user ID from another software system from a User Typeahead field. I can populate a user field with the ID from the external software. I can then use a calc field to display certain other user attributes from that Typeahead. Since we can't calculate custom fields from a typeahead fie...

I concur with Kellie, you're going to have to edit each automation to filter out where you don't want the automation to affect.

That's because you're creating a new database entry with each conversion, with its own ref number. If you preserve the original issue as Doug mentioned, you can reference it with the resolvable object on the new object.

This sounds like a fun puzzle. If you could post your code, I'd be interested in noodling with it.

In some other languages, MM means "many to many" and OM means "one to many".

I agree with both Doug and Skye. One "workaround" I have used is not to sort by if a form exists but by if it's been filled out. To achieve this, put a required field on a form and then group by that field.  If it hasn't been filled out, it might as well not exist.

To add to Doug's correct answer; the more you sort or group, the slower it goes—more collection columns=more processing time, more calc fields=slower display times, etc.

    displayname=Predecessor(s) listdelimiter=<br> listmethod=nested(task.predecessors).lists textmode=true type=iterate valueexpression=CONCAT("(Task#: ",{predecessor}.{taskNumber},") - ",{predecessor}.{name}," - ",{predecessor}.{assignedTo}.{name}," - ",{predecessor}.{plannedCompletionDate}) valuef...