Here is a brief guide on weather you should create one ticket for multiple issues or one ticket per issue.

Ticket request Tips

Each issue that needs to be addressed should be on its own ticket, reasoning is… See this case as eg, A ticket was created for…

• We need the network point Jane is using to be repaired.
• We also need a point for the AP to be installed.

This is technically 3 tickets as there are 3 issues or things to do

• Jane - repair network point
• CABLE a point for the AP that is to be installed, AP is not onsite yet so a separate issue/job
• When the AP is on site, then it needs to be installed (as its not on-site at the time of the request to cable it is a separate and new ticket

The reason for the separation is that each can get their own issues/delays and each can also be completed without the need for the other.
If the AP point cabling hits a snag or delay that impacts the resolution and closure of the install of the AP and ticket, or if the cabling is done but there's no AP (as it may well have been in the case) the cabling ticket cant be closed off.

So to us, the simple way way look at it is,

• Each issue on its own ticket, that way as each is resolved that issue/ticket can be closed.
  
• Also as with the AP and cabling, if the AP arrives later than when the cabling is done, it requires the tech to revisit the site on a different day that's also a separate ticket/callout.
  

Hope this clarifies a little when separate tickets are needed


PLEASE NOTE
By using email the only information available for the tech is the information that you enter in your email or ticket.
Note as much information and all the steps taken, as well as what it is that you need the tech to do.