Managing and completing tickets is an essential part of keeping the business operating. Because we have our own tech in the company, we need to make sure we are always improving the platform, fixing bugs, and creating new features. All of which to make our team and Patients lives easier. Below is a breakdown of how you handle the ticket after it is created. Remember, you are the Project Manager.
Instructions
This ticket should only be read and followed by Creating a Development Ticket
⚠️ You must know the development basics to understand what to check, test, and see the process the developers need to follow.
Because most tickets will be bug tickets, you must look at the estimate and due date the dev put on the ticket to know when it should be done. This is great for planning and potentially communicating with team members.
You will know that the ticket is being worked on when the dev moves the ticket to the In Development column.
Make sure that the dev is on track to complete when they said. This is the most important aspect of what you will be doing. If you are not following up and making sure it is going to get done on time, I promise it will not!
When the dev has completed the task, they will move the ticket to the Staging QA column.
⚠️ The staging server is automatically turned off to save money. In most cases you will need to turn on the staging server through Postman in order to test. Here is the endpoint.
When testing by yourself or with the dev, make sure to go through each point that is written in the ticket. Making bold, what is good and is fixed or built. Test a lot of different scenarios.
⚠️ If we do not test great, we will more than likely push code and create an issue for everyone. I promise someone will contact you. Let’s make sure it’s all tested perfectly!
When you have gone through everything together and feel good about it, move the ticket to Ready for Release column.
The dev should only push the code at a time when no one is working. We should also be checking it when no one is working.
When they push the code, they should test it themselves quickly and move the ticket to the Production QA column.
Now that it is Production QA, you will need to test it right away on the production server by yourself. Test all scenarios and take your time.
⚠️ If there is an issue you find, you must comment in the ticket, provide proof and move the ticket back to In Developerment. Make sure to let the dev know they need to fix ASAP!
If everything is working good, move the ticket to Done column and move on to the next ticket.
Comments (0)