Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2347

Support Manager: Allow tickets to be re-assigned

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.0.0-b5
    • Fix Version/s: Sponsored, 4.7.0-b1
    • Component/s: Plugins
    • Labels:
      None

      Description

      1. Add a new action for selected tickets to "Assign" them to a client. The client will need to be selected, which can be done through a client autocomplete lookup
      2. Assign all selected tickets to the client selected
        • Only tickets that currently have no client assigned may be assigned to one
        • Any tickets can be reassigned to another client, or from no client to a client
      3. Add a note to the ticket for admins to see if a ticket is reassigned from one client to another
        • "This ticket was re-assigned to [Client Name]. Previous client replies were re-assigned to this client and may have been made by another person."

      It's often necessary to assign or re-assign a ticket to a client. As an example, a client may email in a ticket from an email address that's not on file, or may open a ticket under the wrong account.

      Staff should be able to re-assign a ticket. There's a couple scenarios that this might be accomplished:

      1. On the ticket reply screen, add a link or button next to the Client's name or email address, when clicked a search box appears that uses an AJAX search similar to a staff member opening a new ticket for a client.

      2. By adding a new option under the Ticket Overview page where one or more tickets may be selected on the left, where a "Reassign" option appears in the bottom right similar to bulk merge and bulk update status.

        Activity

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              5/Sep/19

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours, 58 minutes
              2h 58m

                Agile