Environments & Logins

The purpose of the dev request ticket is to give a description for the dev team on why something is not working or what is not working. The dev team can then see what they should work on.

There are two processes to follow:

• How to create a Dev Request ticket in Odoo.
• Team leader confirming the ticket.

How to create a Dev Request ticket in Odoo

• Log in to Odoo with your username and password.
• From the menu bar, click on Project.

• From the side panel on the left, click once on Issues.

• Click on the Create button to create a ticket.

• Complete the correct information:
• Issue: The name of the ticket.
• Tags: The applicable tag for the ticket.
• Project: Choose the correct project from where the Dev request is requested.

• Click on the Description tab and enter the description in the description box.

NB: The description should be in English, don't use too long sentences or any funny characters. Type only what is related to the Dev request.

• Click on the Steps to Reproduce tab, type in what is wrong and how it happened.

• Click on the Requirement tab.

• Complete the following information:
• Stakeholder: Put in your own name so that the Dev team knows to whom the feedback is.
• Client Priority: Choose the correct priority.

• Low: It is nice to have a function.
• Medium: It will make a difference in the daily procedures.
• High: It is needed and influences the client's daily procedures and blocking the client to work effectively.
• User Role: For which user role is the request.
• Reason: Why you are putting in a request, to understand it better.
• Requirement Type: You have an option from the drop-down to choose from.

• Choose the correct requirement type:
• Business Requirement: The practice feels that they want a dev request for their business.
• System Requirement: The GoodX system is lacking the function.
• User Requirement: The receptionist or Dr feels that they lack the function on their side.
• Internal Requirement: The practice feels that it will make a difference in their processes. It can also be an internal requirement for GoodX, depending on the dev request.
• Expected Behaviour: What you think the system must do.

• Click on the Save button, to save your ticket.

• Click on the Discard button to exit without saving.

• If applicable Click on Attachments to attach a Screenshot, Image, Video, File, or anything that will help the developers better understand the Dev Request.

• Or Log an internal note where you can also add an attachment.

• Your ticket will then go through to the team leaders and the management team of that specific team. The team leader is not part of the dev team.

Team leader confirming the ticket:

• The team leader or management will Click on the Approved button.

•  The System will give an error if everything wasn't filled in, click on the OK button and complete the form.

• Once Approved the Project Type will change to GoodX Dev and the process stage will change to Dev/Request.

• When Approved the Approval Confirmed box will automatically be ticked.

Take Note: Once you clicked on the Approved button and it is Approved, you cannot click on it again, the system will give you a warning.