Create a task report
The video provides a step-by-step guide on creating a custom report to track late tasks assigned to the logged in user. It begins by explaining the need for custom reports when existing filters, views, or built-in reports don鈥檛 meet specific requirements. 鈥 The report is named 鈥淟ate Tasks Assigned to Me,鈥 with a description added for clarity. 鈥
The resulting report helps users focus on late tasks, provides insights into dependencies, and simplifies navigation to the host projects. 鈥
Key takeaways
- Custom Report Creation: When existing filters and built-in reports don鈥檛 meet your needs, you can create a custom report from scratch to focus on specific data, such as late tasks assigned to you. 鈥
- Filter Setup: Use filters to define report criteria, including late tasks, incomplete tasks, current projects, and tasks assigned to the logged-in user. 鈥
- Columns for Context: Add columns like 鈥淐an Start鈥 to identify dependency issues and 鈥淧roject Name鈥 with hyperlinks for easy navigation to related projects. 鈥
- Sorting for Priority: Sort tasks by the 鈥淒ue On鈥 column in ascending order to prioritize the most overdue tasks at the top of the report. 鈥
- Accessibility: Save the report, pin it, or mark it as a favorite for quick access, ensuring efficient tracking and management of late tasks.
鈥淐reate a task report鈥 activities
We鈥檝e gathered favorite reports from customers and put them together in a snackable, easily digestible, cookbook for you to take back and test out in your own Workfront kitchen.
These 10 reports come from customers who are just like you. Spread out across industries, departments, teams, positions and all in different companies, we owe a huge thank you to the incredible customers who shared one of their favorite reports. Some reports are simple (but incredibly useful), and some are more complex to take your reporting to the next level.
Activity 1: Create a note report with prompts
Create a Note report that you can use to search for user notes (i.e., comments or updates) or system notes based on the note content, the author, entry date, project name, or audit type. Name the report 鈥淣ote Search.鈥
When using the Note Text prompt, this report will search within update threads to quickly extract any that meet the criteria specified in the prompts. When you run the report, you don鈥檛 need to fill in every prompt, just the ones you care about. The blank ones are automatically ignored.
The view should include columns for:
- Note Text
- Audit Text
- Entry Date
- Owner: Name
- Audit Type
- Task Name
- Issue Name
Leave the filter tab blank.
Group on Project Name.
Include prompts for the following:
- Audit Text
- Note Text
- Owner Name
- Entry Date
- Project Name
- Audit Type
Answer 1
-
Select Reports from the Main Menu.
-
Click the New Report menu and select Note.
-
In Columns (View) set up your columns to include:
- Note > Note Text
- Note > Audit Text
- Note > Entry Date
- Owner > Name
- Note > Audit Type
- Task > Name
- Issue > Name
-
Select the Entry Date column and change the Sort to Descending.
-
In the Groupings tab, set the report to group by Project > Name.
-
Leave Filters blank.
-
Open Report Settings and name the report 鈥淣ote Search.鈥
-
In the Description field, put something like, 鈥淪earch for System or User notes based on the Audit Type selected and other prompts. System notes appear in the Audit Text column and User notes appear in the Note Text column.鈥
-
Select Details Tab so that it displays when the report loads.
-
Set the report to show 200 items when the report is included on a dashboard.
-
Click Report Prompts and add:
- Note > Audit Text
- Note > Note Text
- Owner > Name
- Note > Entry Date
- Project > Name
- Note > Audit Type
-
Check the box for Show Prompts in Dashboards.
-
Save and Close your report.
Activity 2: Create an admin team feedback report
This is an issue report that displays all the issues from a feedback request queue created for system admins. You can see how to create this request queue in the Create a system admin feedback request queue tutorial.
This report also uses a custom form. To learn how to create a custom form, see the Create and share a custom form tutorial.
This custom form should use object types Project and Issue, and should be created as follows:
Name: Admin process feedback
-
Process type (single-select dropdown field)
- access levels
- approval process (global only)
- email notifications
- layout template
- milestone path
- project template
- reminder notifications
- request queue
-
Process name (single line text field)
-
Process grade (single-select dropdown field)
- 1 - totally useless
- 2 - not very useful
- 3 - good but could be better
- 4 - excellent
-
Problem or good news (paragraph text field)
Create an issue report named Admin team feedback report.
The view should have the following columns:
- Issue: Name
- Primary Contact: Name
- Issue: Process type
- Issue: Process name
- Issue: Process grade
- Issue: Problem or good news
- Issue: Entry date
- Issue: Age
- Issue: Assignments
- Issue: Status
Group on Process type.
Filter on the ID of the request queue project where the feedback issues reside.
Answer 2
-
Select Reports from the Main Menu.
-
Click the New Report menu and select Issue.
-
In Columns (View) set up your columns to include:
- Issue > Name
- Primary Contact > Name
- Note: this appears with 鈥淥wner:Name鈥 as the column label. You can change this to 鈥淩eported by鈥 by clicking on Advanced Options and typing 鈥淩eported by鈥 in the Custom Column Label field.
- Issue > Process type
- Issue > Process name
- Issue > Process grade
- Issue > Problem or good news
- Issue > Entry date
- Issue > Age
- Issue > Assignments
- Issue > Status
-
Select the Entry Date column and change the Sort to Descending.
-
In the Groupings tab, set the report to group by Issue > Process type.
-
In the Filters tab, add a filter for the Issue > Project ID to equal the request queue project where the feedback issues reside.
-
Save and Close your report.