That is correct. It sounds like your request queue is not configured to take full advantage of routing rules. Using routing rules is always advised. This allows you to make a queue broadly accessible to many/all users and depending upon the queue topic they select to submit their request, it is rout...

Yes, I was informally using the term "parent" to indicate the record (task or issue) to which the assignment belongs. The new shared column described above will display all users assigned, whether it's a task or an issue. It does not look at any parent/child task relationships. 

If you only need/want to display all User assignments (ignore role-only and team assignments) of the parent task or issue in an assignment report: 1. add below text mode to a new column in your assignment report:  displayname=All Assignments listdelimiter=<div> listmethod=nested(task.assignments).li...

It depends on what kind of report you are making. It looks like a Task report. If so, everything you've listed can be done out of the box. If this task report is meant only for parent tasks as mentioned in the earlier thread, you can include "Task >> Parent ID = is blank" in your filter rule.

I am presuming that your goal is to pull in all assignees of the task or request from which the assignment was created, and not just the assignment assignee? (e.g. if three users are assigned to one task, that generates three assignment records with one assignee each) The assignment-specific assigne...

Adding inline search to the New Request pill was a big improvement, but agree that it doesn't address the challenges shared above. We ended up creating a "Request Directory" custom section in our Requests landing page, so users can scroll the various queues, groups, or topics along with relevant des...

I raised this question back in 2018 (almost to the day! - five years has really flown by...)The same question was raised again in 2022 by another user, and at that time a workaround was identified to enable line breaks in calculated fields.I'm linking to that newer thread from here for any users who...

Nice work, Ross!(don't forget to mark your own answer correct so you get the credit )

Not sure if I understood correctly, but will take a stab: - A project is opened and there are 10 tasks assigned to "Graphic Designer" role. - "User X" (no job role assigned) is assigned to those 10 tasks. - Because User X doesn't have the Graphic Designer role assigned to them, each task now has 2 a...

The "Misc Action" module makes this easier than the "Custom API" module does, but either can work. "Misc Action" would look like this: If you must use Custom API call module, you need to pass the arguments as JSON in the request body; not as parameters in the query string:    Good luck!