charts work by using real fields - not merged columns. The best way to handle this would be to create a calculated field on the form that merges the two names together and then chart using this field.

For single users whose email address changes, you would deactivate the user and edit them to make the change. Reactivate when you're done. (edited to add, we would do all this in Workfront)

I think it would work to use the same code from here: https://experienceleaguecommunities.adobe.com/t5/workfront-questions/how-to-find-all-users-who-do-not-belong-to-a-specific-group/m-p/483004#M15773   and then separate your two groupIDs with a tab.

You can learn more about these types of filters by running a search in the community on "ARVSTS". There are only 5 results, so I absolutely recommend just tucking in and digesting it all.  https://experienceleaguecommunities.adobe.com/t5/custom/page/page-id/GlobalSearch#q=ARVSTS&sort=relevancy&f:@el...

this may not be the right solution for you either, but just want to remind you that it's quite common for teams to set up sharing rights at the template level, such that each team's projects, when created, are already shared to a point where the entire team and hence manager, can see them. It just m...

I got the following from copilot after feeding it some expectations from out of the calculated data expressions page here:   https://experienceleague.adobe.com/en/docs/workfront/using/reporting/reports/calculated-custom-data/calculated-data-expressions    displayname=Extracted Texttextmode=truevalue...

totally get it -- misread your last reply thinking you were talking about task OR issues, two separate reports -- but you're talking about tasks or issues into one report, so -- unfortunately, my initial answer will still stand -- having both the tasks and issues in one report, they will still sort ...

If you're only doing tasks or only doing issues and this is just for a specific individual, I think you should just group them (using the collapse option to group) and then show using the detail view. It gives the same effect as the grouping, but will sort correctly, which the summary page never see...

There's no such thing as a "task and issue report" so judging by what you've attached, I'm wondering if maybe you're talking about an assignment report or a work item report. You appear to be trying to combine two different fields (request and task priority based on whether something is a request or...

so to clarify, is it possible that the users who have the calendars had previously clicked into the calendar area, whether accidental or on purpose, and thus automatically generated a calendar -- or are you saying that all users have never clicked into the calendar area?