- APPS
- Helpdesk Project Integration 19.0
| Lines of Code | 1104 |
| Technical name | viin_helpdesk_project |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/19.0/viin_helpdesk_project |
| Read description for | v 17.0 v 18.0 |
| Required Apps | Project (project) Discuss (mail) |
| Included Dependencies | Helpdesk Viindoo Base |
| Extensions | Helpdesk Timesheet Integration |
Every support ticket stays linked to the project work it causes
For companies whose support team and project team serve the same customers
The ticket that turned into work
Odoo 19.0 · Community and Enterprise · OPL-1
Extends Helpdesk: its tickets gain a project and a task, and its teams a default project.
What changes for your team
A ticket becomes planned work, without retyping
An agent copies the ticket into a task by hand, and the customer's messages and files stay behind in support.
→ Convert to Task creates the task in the project you choose, with the ticket's description, messages and attachments. A ticket that stays open gets a linked task instead, and a task that is really a customer request becomes a ticket.
Project managers see the support behind each project
A project manager hears about customer issues on the project when someone forwards an email.
→ Each project card counts the open tickets of the project's own support team and of other teams. The project and each task open their tickets in one click.
Customers report an issue from the project they follow
Customers write to the project manager, who forwards the issue to support and loses track of it.
→ On the portal, a shared project and each of its tasks offer Create Ticket. The ticket goes to the project's support team when that team accepts portal tickets, and its page shows the project and the task.
Ready on day one
Project and task on every ticket
Search, filter and group tickets and the ticket report by project and task.
Read access for followers
An employee who follows a project or a task reads its tickets, without joining the support team.
Installs itself
Once Helpdesk and Project are both installed, this module is installed with them.
What you set up first
A default project for each support team, a support team for each project and, for customers, projects shared on the portal.
What is included
The link between tickets, projects and tasks in both directions, the conversions, the ticket counts on projects and tasks, and ticket creation from the portal pages of a project or a task. Teams, stages and SLA policies come from Helpdesk.
Optional extension
Helpdesk Timesheet Integration
Agents log their hours on each ticket, so you see what a customer's or a project's tickets cost.
Before you decide
Is anything lost when a ticket becomes a task?
No. Messages and attachments move to the new record, and the original is archived, not deleted.
Who sees the tickets of a project?
Support staff see tickets as Helpdesk defines. An employee who follows the project or task can read its tickets but not change them. Linking and converting need Project user access.
Can a ticket have several tasks?
No, a ticket has one task. A task can have several tickets.
We run several companies. Can tickets cross between them?
No. A project takes only support teams of its own company, and a conversion between companies is refused with a message.
Which languages does it ship?
English and Vietnamese.
Try it, then ask us
The Documentation tab walks through the setup and the work of each role, from the support agent to the customer on the portal, screen by screen.
Pre-sales & partnership
viindoo.com/contactusTechnical support
viindoo.com/ticketTechnical requirements
- Odoo version: 19.0
- Editions: Community, Enterprise
- Required modules: Helpdesk, Project
- License: OPL-1
- Languages: English, Vietnamese
Helpdesk Project Link
Who this guide is for: support agents who also work in Projects, project managers, the person who sets up the support teams, and the customers who follow a project in the portal.
Note
Extends the Helpdesk application - see the viin_helpdesk documentation for tickets, teams, stages and the customer portal in general.
Overview
A ticket often needs real work: a fix to plan, a change to schedule, a visit to organise. This module keeps the ticket and that work linked, in both directions:
- a ticket shows its Project and its Task;
- a task shows the tickets it belongs to, and a project shows all of its tickets;
- a ticket can be turned into a task, and a task into a ticket, without retyping anything;
- a customer files a ticket directly from the project or task they follow in the portal.
How the work flows:
- A ticket arrives in a support team (from the customer portal, an email or an agent).
- The support agent links it to a task, or converts it into one, so the work is planned in the project.
- The project manager follows the tickets of the project from the project screen.
- The customer sees the project and the task on the ticket page.
| Who | What they do | Access right to assign |
|---|---|---|
| Support agent who is a project user | Links tickets and tasks, creates a task from a ticket, converts a ticket into a task and a task into a ticket | Helpdesk / User and Project / User |
| Project manager | Follows the tickets of a project and of its tasks; sets the support team of a project | Project / Administrator |
| Helpdesk administrator | Chooses the default project of each support team | Helpdesk / Administrator |
| Customer | Files and follows tickets from the project or task page of the portal | Portal user, invited on the project |
Setup (for the administrator)
Installation
- Open Apps.
- Search for Helpdesk Project Integration and press Install. The Helpdesk and Project apps are installed with it if they are missing.
Choose the default project of a support team
Tickets of a team can start in a project automatically.
- Open Helpdesk ‣ Configuration ‣ Helpdesk Teams and select the team.
- Open the Project tab.
- Choose the project in the Project field and save.
From then on, a new ticket of this team is placed in that project, and its agents can link the ticket to a task of that project.
Choose the support team of a project
Open the project (Project ‣ Projects) and fill Helpdesk Team. It is the team that receives the tickets created from that project, and the team a customer is offered when they file a ticket from the project page of the portal.
A project without a company chooses among all the teams you can see. A project of a company chooses among the teams of that company, and a team of another company is refused with a message.
Note
A ticket form opened from a project or from a task proposes the project's team only when you are allowed to read that team; otherwise it proposes the company's default team, and none if you can read neither.
Give a customer access to a project
A customer sees the project, its tasks and the Create Ticket button in the portal when the project is shared with them (visibility Invited internal and portal users and the customer added as a follower), and when at least one support team accepts tickets from the portal. A team accepts them when its Visibility is Portal users and Invited internal users.
Support agent
Open the project and the task of a ticket
Open Helpdesk ‣ Tickets ‣ All Tickets and select a ticket. The Project field is filled from the team's default project; change it if the ticket belongs to another project. Once the ticket has a project, the Task field appears and lists the tasks of that project.
Choosing another project empties the Task field when the task belongs to a different project.
Create a task for a ticket
- Open the ticket and press Create Task. The button is shown to project users while the ticket is active and has no task.
- The Tasks screen opens in the ticket's project. Press New: the new task starts with the ticket's title.
- Complete the task (assignees, stage, deadline) and save it.
The task is linked to the ticket: the Task field of the ticket shows it, and Create Task is not offered. A ticket has one task: a task created later from the Tasks screen does not replace it. To follow the ticket with a different task, change the Task field.
Convert a ticket into a task
Use this when the ticket becomes pure project work and should leave the support queue.
- Open the ticket and press Convert to Task.
- In Convert to Tasks, choose the Project. The Partner and the project are proposed from the ticket. Optionally tick Assign To Me, set a Deadline and add Tags.
- Press Create Task.
The task is created with the ticket's title, description, and the ticket's attachments and messages. The ticket is archived. The company of the ticket must be the company of the project, otherwise the conversion is refused with a message.
Create a ticket from a task
Use this when a task needs a follow-up with a support team and the task itself must stay open.
- Open the task (Project ‣ Tasks) and press Create Ticket beside Convert to Ticket.
- A new ticket form opens, filled from the task: its title, the task, the task's project and the project's team when you may read it. Choose the Ticket Type, complete the ticket and save it.
The task is not changed. Convert to Ticket, below, differs: it archives the task and moves its messages and attachments to the ticket.
Note
If you can read no helpdesk team, Create Ticket and Convert to Ticket tell you that no helpdesk team is available to you. Ask a helpdesk administrator to add you to a team or to open a team to you.
Convert a task into a ticket
Use this when a task is really a customer request that belongs in a support team.
- Open the task (Project ‣ Tasks) and press Convert to Ticket.
- In Convert to Ticket, check the Partner, the Ticket Type and the Helpdesk Team (the project's team is proposed). Tick Send Notification Email if the partner should be told when the ticket changes stage. Assign To Me appears when you are a member of the chosen team.
- Press Create Ticket.
The ticket is created with the task's title and description, linked to the task, with the task's attachments and messages. The task is archived. The company of the task must be the company of the team.
See the tickets of a task
The task shows a Tickets button with the number of linked tickets. Press it to open the ticket (when there is one) or the list of tickets. From the list, New starts a ticket with the task's title, description, customer and the project's team.
Filter and group tickets by project and task
Helpdesk ‣ Tickets ‣ All Tickets opens with the Open filter on, so resolved and cancelled tickets are hidden; remove the filter to see them. In that list and in Helpdesk ‣ Reporting, search by Project or Task, filter the tickets that have a project or a task, and group them by project or task. In the ticket list, show the Project and Task columns from the optional columns menu.
Project manager
Follow the tickets of a project
On the project form (Project ‣ Projects), the Ticket button shows how many tickets belong to the project and opens them. A new ticket created from that list starts in the project, with the project's customer and support team.
On the project card of the kanban view, the menu has a Tickets entry, and two counters show the open tickets of the project:
- Same Team Tickets - the open tickets handled by the project's support team;
- Different Team Tickets - the open tickets handled by any other team.
A ticket is open while its stage is not folded. Resolved and Cancelled tickets are closed and are left out of both counters. Press a counter to open that list: it shows the same tickets as the number. A counter is hidden when it is zero.
Follow a ticket without support access
An internal user who follows a project or a task can read the tickets linked to it, without being a member of the support team. They cannot change them.
Customer (portal)
File a ticket from a project
- Sign in to the portal and open Projects, then the project.
- Press Create Ticket.
- Fill in the Title, the Helpdesk Team, the Type and the Description, add attachments if useful, and press Submit. When the project has a support team that accepts portal tickets, that team is the one offered; otherwise the customer chooses among the teams that accept portal tickets.
The ticket is linked to the project. Its page shows the Project and, when a task is linked, the Task.
File a ticket from a task
On a task page, Create Ticket files a ticket linked to the project and the task, and View All Tickets lists the tickets of that task.
Troubleshooting
- The Create Task button is missing on a ticket.
- The ticket already has a task, the ticket is archived, or you do not hold Project / User.
- The Task field is missing on a ticket.
- The ticket has no project yet. Choose a project, or set a default project on the team.
- The Helpdesk Team list of a project is empty.
- You can read no team, or the project belongs to a company that has no team. Ask a helpdesk administrator to open a team to you, or to create one for the company.
- Choosing a team of another company on a project is refused.
- A project of a company takes only the teams of that company. Choose a team of the project's company.
- Create Ticket says no helpdesk team is available to me.
- You can read no helpdesk team. Ask a helpdesk administrator to add you to a team or to open a team to you.
- Create Ticket does not appear for the customer.
- The project is not shared with the customer, or no support team has Visibility set to Portal users and Invited internal users.
- A conversion is refused with a company message.
- The ticket and the project (or the task and the team) belong to different companies. Convert into a project or a team of the same company.
FAQ
- Can a ticket have several tasks?
- No, a ticket has one task. A task can have several tickets.
- Are the messages and files kept when I convert?
- Yes. Attachments and messages of the converted record move to the new one, and the converted record is archived.
- Can I undo a conversion?
- The archived record is not deleted: unarchive it from the list of archived records if you need it again.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.