Zadania Szkoleniowe PQM
Szkolenie PQM / Tasks, Add Task and Production List
Tasks, Add Task and Production List
Create, read and manage production tasks with clear instructions, deadlines, departments, notes, files and statuses.
Training HomeProduction DashboardCore ConfigurationTasks and Add TaskDepartments and WorkflowCalendar and Standard GanttEmail Queue and CommunicationReports and KPIModules / MarketplaceSetup WizardLicense and Demo ModeHelp and TrainingAdmin PanelClient PanelEmployee Worker PortalShop Manager / SupervisorImplementation Checklist
Purpose in plain language
Tasks are the heart of PQM. A task is a single production job with its own customer/order information, status, department, deadline, notes, files, costs and communication. If the task is clear, the production team knows what to do. If the task is unclear, the whole system becomes noise.
For a beginner, the key rule is simple: create tasks carefully and update them regularly. Reports, calendar, email notifications and portals all depend on task data.
Where to click
Add Task: field-by-field explanation
| Field / area | What it means | What a beginner should enter |
|---|---|---|
| Task title / name | Short production name used in lists and dashboards. | Use a clear name: “Business cards for ACME – 1000 pcs”, not “urgent job”. |
| Customer / order | Who the work is for or which WooCommerce order it belongs to. | Select the customer/order when available. If it is an offline job, enter enough information to identify the client. |
| Department | The first or responsible production stage. | Choose the department that should start or currently own the task. |
| Status | Current production state. | Use “New” or similar when creating. Change status only when real work state changes. |
| Deadline / due date | When the task should be completed or delivered. | Enter the realistic date promised to customer or required by internal planning. |
| Priority | How urgent the task is compared to normal work. | Use high priority only for truly urgent tasks. If everything is urgent, nothing is urgent. |
| Production notes | Internal instructions for employees. | Write exact requirements: material, quantity, format, finishing, packaging and customer comments. |
| Files / artwork | Production files, proof, invoice, graphics or attachments. | Attach the right file version and describe it if several versions exist. |
| Costs / time | Information used for margins and production analysis. | Enter labor/material costs when the workflow requires it. Incorrect cost data creates misleading margin reports. |
Create a task step by step
Task List: how to read it
The task list is the operational table of production. It should help a manager answer: what is open, what is late, who is responsible and what should be done next.
| List element | Meaning | How to use |
|---|---|---|
| Search box | Finds task by title, number, customer, order or keyword depending on configuration. | Use when a customer calls and gives only a name/order reference. |
| Status filter | Shows only tasks in selected state. | Use to review only new, in progress, completed, cancelled or complaint tasks. |
| Department filter | Shows work assigned to a stage/team. | Use during department meetings or when checking bottlenecks. |
| Date filter | Limits tasks by created, due or completed dates depending on the report/list. | Use before monthly reports or weekly planning. |
| Task row | One production job. | Click the title/number/view button to open details. |
| Actions | Open, edit, change status, send message, view order or export depending on role. | Only use actions that match real workflow. Do not change status without checking the task. |
Simple production lifecycle
Cancelled and complaint tasks are special cases. They should be visible when needed, but they should not distort normal production statistics.
Beginner examples
“Print 500 A5 flyers, 170g gloss, 4/4, trim to final size. File: flyers_final_v3.pdf. Deliver to customer reception by Friday 10:00. Check blue color on proof before full run.”
“Flyers. Urgent. Ask Mark.” This does not tell the employee what to print, which file to use or when it is needed.
Good practice
- Every task should have a responsible department, deadline and clear instruction before production starts.
- Use comments/notes for production facts, not private discussions that should not be stored with the job.
- Do not use completed status until the task is actually finished.
- When a customer changes requirements, update the task notes so the whole team sees the newest version.
- Use cancellation status for cancelled jobs instead of deleting tasks. History is valuable.
Screenshot reference
Click any screenshot to open it in a new tab. This is useful for zooming in while following the step-by-step instructions.
Task list reference. Use it to explain filters, statuses, search, columns and how to open a task.
Who should use this screen?
Troubleshooting for beginners
| Symptom | Simple explanation | What to check first |
|---|---|---|
| The page looks empty | The system may have no demo data yet, or the current user may not have access to the required role/capability. | Create one test task, assign a department, then refresh the screen. Also check the user role. |
| A button opens a login page or My Account | The visitor is not logged in or the page is using a frontend-safe route that requires authentication. | Log in with a test user that has the expected role. Check whether the shortcode/page is visible only to logged-in users. |
| Data exists but does not appear in a report/chart | Filters, date range, status rules or completion dates may exclude the task. | Clear filters, expand the date range and verify that the task has the status/date required by the report. |
| Something changed but the screen still shows old data | Browser cache, WordPress cache or AJAX response cache may show old information. | Refresh the page, clear cache for this page and test in an incognito window before debugging code. |
| The layout is broken on a small screen | Wide tables and timelines need horizontal space; this is normal if the content remains readable. | Use the mobile breakpoint, keep cards in one column and allow horizontal scroll only inside tables/timelines. |



