Details
Description
I think this can be simplified by simply allowing staff or the client to add additional addresses via CC, perhaps limit 5 maximum or something. If a ticket comes in via email and has users CC'd, include them automatically as CC's on the ticket. Staff and the client can add CC'd users via the web interface.
History Below
Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts
When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response.
This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both.
- Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket
- When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket
- When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request)
NOTE!
In addition to being able to select existing contacts to loop into this ticket, staff and the client should both be able to add email addresses as a "CC" in effect, to the ticket. The ticket system should accept an email reply from someone who was CC'd on the ticket, whether that is a contact that was assigned, or an email address added to the ticket.
The use case for allowing any email address to be added to a ticket, allows staff or the client to loop in another party who may be able to help with the issue at hand, but whom should not be a contact. For example, looping in someone from a data center to help diagnose an issue.
Activity
Field | Original Value | New Value |
---|---|---|
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked lower |
Rank | Ranked higher |
Description |
Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts
When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response. This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both. # Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket #* When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket #* When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request) |
Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts
When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response. This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both. # Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket #* When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket #* When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request) NOTE! In addition to being able to select existing contacts to loop into this ticket, staff and the client should both be able to add email addresses as a "CC" in effect, to the ticket. The ticket system should accept an email reply from someone who was CC'd on the ticket, whether that is a contact that was assigned, or an email address added to the ticket. |
Description |
Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts
When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response. This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both. # Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket #* When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket #* When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request) NOTE! In addition to being able to select existing contacts to loop into this ticket, staff and the client should both be able to add email addresses as a "CC" in effect, to the ticket. The ticket system should accept an email reply from someone who was CC'd on the ticket, whether that is a contact that was assigned, or an email address added to the ticket. |
Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts
When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response. This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both. # Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket #* When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket #* When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request) NOTE! In addition to being able to select existing contacts to loop into this ticket, staff and the client should both be able to add email addresses as a "CC" in effect, to the ticket. The ticket system should accept an email reply from someone who was CC'd on the ticket, whether that is a contact that was assigned, or an email address added to the ticket. The use case for allowing any email address to be added to a ticket, allows staff or the client to loop in another party who may be able to help with the issue at hand, but whom should not be a contact. For example, looping in someone from a data center to help diagnose an issue. |
Rank | Ranked higher |
Description |
Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts
When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response. This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both. # Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket #* When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket #* When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request) NOTE! In addition to being able to select existing contacts to loop into this ticket, staff and the client should both be able to add email addresses as a "CC" in effect, to the ticket. The ticket system should accept an email reply from someone who was CC'd on the ticket, whether that is a contact that was assigned, or an email address added to the ticket. The use case for allowing any email address to be added to a ticket, allows staff or the client to loop in another party who may be able to help with the issue at hand, but whom should not be a contact. For example, looping in someone from a data center to help diagnose an issue. |
I think this can be simplified by simply allowing staff or the client to add additional addresses via CC, perhaps limit 5 maximum or something. If a ticket comes in via email and has users CC'd, include them automatically as CC's on the ticket. Staff and the client can add CC'd users via the web interface.
*History Below* Feature request @ https://requests.blesta.com/topic/support-tickets-specify-ticket-contacts When an admin replies to a ticket for a client, the primary client contact and other contacts may receive the ticket response. This task will add a section on the ticket in the admin UI to specify the contacts that will receive ticket responses via email. How this looks in the UI should be considered, but I imagine we will need to know both the contact's name and their contact type. It may also be useful to know their email address since some contacts may have the same email address as the primary contact and there wouldn't be a need to send the email to both. # Update the admin UI to send an admin's ticket reply to a subset of the client contacts as defined on the ticket #* When an admin replies by email, only ticket defined ticket recipients should receive an email notice about the ticket #* When an admin replies by UI, the UI should allow the ticket contacts to be updated, and the email reply should be sent to the updated list (i.e. both occurring in the same request) NOTE! In addition to being able to select existing contacts to loop into this ticket, staff and the client should both be able to add email addresses as a "CC" in effect, to the ticket. The ticket system should accept an email reply from someone who was CC'd on the ticket, whether that is a contact that was assigned, or an email address added to the ticket. The use case for allowing any email address to be added to a ticket, allows staff or the client to loop in another party who may be able to help with the issue at hand, but whom should not be a contact. For example, looping in someone from a data center to help diagnose an issue. |
Fix Version/s | 5.11.0-b1 [ 11908 ] |
Rank | Ranked higher |
Sprint | 5.11.0 Sprint 1 [ 194 ] |
Assignee | Abdy Franco [ abdy ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 7 hours, 54 minutes [ 28440 ] | |
Worklog Id | 16852 [ 16852 ] |
Time Spent | 7 hours, 54 minutes [ 28440 ] | 1 day, 7 hours, 50 minutes [ 57000 ] |
Worklog Id | 16853 [ 16853 ] |
Time Spent | 1 day, 7 hours, 50 minutes [ 57000 ] | 2 days, 7 hours, 48 minutes [ 85680 ] |
Worklog Id | 16854 [ 16854 ] |
Time Spent | 2 days, 7 hours, 48 minutes [ 85680 ] | 3 days, 5 hours, 34 minutes [ 106440 ] |
Worklog Id | 16855 [ 16855 ] |
Time Spent | 3 days, 5 hours, 34 minutes [ 106440 ] | 4 days, 3 hours, 51 minutes [ 129060 ] |
Worklog Id | 16859 [ 16859 ] |
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Sprint | 5.10.0 final [ 194 ] | 5.10.0 final, 5.11.0 Sprint 1 [ 194, 201 ] |
Rank | Ranked higher |
Sprint | 5.10.0 final, 5.11.0 Sprint 1 [ 194, 201 ] | 5.10.0 final, 5.11.0 Sprint 1, 5.11.0 Sprint 1.5 [ 194, 201, 205 ] |
Sprint | 5.10.0 final, 5.11.0 Sprint 1, 5.11.0 Sprint 1.5 [ 194, 201, 205 ] | 5.10.0 final, 5.11.0 Sprint 2, 5.11.0 Sprint 1, 5.11.0 Sprint 1.5 [ 194, 196, 201, 205 ] |
Rank | Ranked higher |
Sprint | 5.10.0 final, 5.11.0 Sprint 2, 5.11.0 Sprint 1, 5.11.0 Sprint 1.5 [ 194, 196, 201, 205 ] | 5.10.0 final, 5.11.0 Sprint 2, 5.11.0 Sprint 1, 5.11.0 Sprint 3, 5.11.0 Sprint 1.5 [ 194, 196, 201, 202, 205 ] |
Rank | Ranked higher |
Time Spent | 4 days, 3 hours, 51 minutes [ 129060 ] | 1 week, 1 hour, 31 minutes [ 149460 ] |
Worklog Id | 17365 [ 17365 ] |
Time Spent | 1 week, 1 hour, 31 minutes [ 149460 ] | 1 week, 1 day, 1 hour, 30 minutes [ 178200 ] |
Worklog Id | 17367 [ 17367 ] |
Time Spent | 1 week, 1 day, 1 hour, 30 minutes [ 178200 ] | 1 week, 1 day, 2 hours, 29 minutes [ 181740 ] |
Worklog Id | 17368 [ 17368 ] |
Status | In Review [ 5 ] | Closed [ 6 ] |