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

Support Manager: Not-logged-in clients may get no success message when opening a ticket

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 3.2.0-b1
    • Fix Version/s: 3.2.0-b3
    • Component/s: Client Interface
    • Labels:
      None

      Description

      If there is only 1 department visible to a client when not logged in, then the system currently redirects them to add a ticket to that department rather than choose a department from a list of departments. Because of this additional redirect, the success message is lost after creating a ticket.

        Activity

        Hide
        admin Paul Phillips added a comment -

        Should we display the single department rather than redirecting them to add a ticket to that department? This may provide some consistency, while resolving the message issue.

        Show
        admin Paul Phillips added a comment - Should we display the single department rather than redirecting them to add a ticket to that department? This may provide some consistency, while resolving the message issue.
        Hide
        tyson Tyson Phillips (Inactive) added a comment -

        I think you wanted to forward users straight to creating a ticket if there was only 1 department, but we could nix that behavior. Otherwise we need to redirect the user to a separate URL if there is only 1 department available.

        Show
        tyson Tyson Phillips (Inactive) added a comment - I think you wanted to forward users straight to creating a ticket if there was only 1 department, but we could nix that behavior. Otherwise we need to redirect the user to a separate URL if there is only 1 department available.

          People

          • Assignee:
            tyson Tyson Phillips (Inactive)
            Reporter:
            tyson Tyson Phillips (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              9/May/14