OPEN SOURCE / SELF HOSTED VERSION

Features: The feature of open source organization is that they all have their own servers and their own code, so there are many cases where it is only organization. 

 

BUGS CHECKING PROCESS with detailed description

1. We check for issue in the latest updated erxes organization. Usually it is: office.erxes.io. Because we check all new code work in office.erxes.io. Also, most bugs are reported first on office.erxes.io.
   /Because it is written as "Usually", it means that in some cases it is not done, When the data of the client company is too much from office.erxes.io, an issue is sent to the client company first/
2. If the BUG APPEARS IN OFFICE, create a ticket and give it to the developer
3. If the BUG DOESN'T APPEAR IN OFFICE, It need to UPDATE the client's organization. If the issue is not fixed after the UPDATE, the system administrator or the company should update it again until the bug is fixed. 

 

BUG CHECKING PROCESS short

1. Check it office.erxes.io
2. CREATE A TICKET if the is been here office.erxes.io
3. UPDATE if the issue hasn't been office.erxes.io

 
HOW TO CREATE TICKET FOR BUG? /for everyone who find a bug/

1. How to check bugs as a developer? should be thought of and created
2. When doing so, you will be enter to know in detail what SEQUENCE to erxes, where exactly the BUGS, whether it is a VIDEO or a PICTURE, TEXT. 
3. Add customer's info in ticket. In this way, as soon as the bug is fixed, As soon as the bug is fixed, client's organization will be updated
4. In addition, provide the login info of the customer organization and allow the developer to check after the UPDATE

 

HOW TO CHECK FOR BUG? /for developers/

1. The TICKET should be very clear to look at, and it should be such that you don't need to ask anything from anyone. If not, you can write discord SUPPORT channeld saying that the ticket is not clear.
2. After the ticket is completed, it is considered that the ticket is completed by submitting an update to the customer organization.

 

SAAS VERSION

Features: SAAS clients are all ONE SERVER, ONE AWS, ONE CODE, all information is the same, so if one bug occurs, the ALL ORGANIZATION ALSO ISSUE. 

 

BUG CHECKING PROCESS with explanation

1. In any case, check the SAAS account 
2. If there is an BUG, a ticket will be created immediately
3. If there are NO BUGS, the customer's account information will be obtained. Because this is a special case.

 

HOW TO CREATE TICKET FOR BUG? /for everyone who find a bug/

1. How to check bugs as a developer? should be thought of and created
2. When doing so, you will be enter to know in detail what SEQUENCE to erxes, where exactly the BUGS, whether it is a VIDEO or a PICTURE, TEXT. 

 

HOW TO CHECK FOR BUGS? /for developers/

1. The TICKET should be very clear to look at, and it should be such that you don't need to ask anything from anyone. If not, you can write discord SUPPORT channeld saying that the ticket is not clear.
2. After the ticket is completed, the SAAS organization will check it and consider the TICKET completed.