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

Support Manager: Add new custom field options

    Details

    • Type: New Feature
    • Status: In Review
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.10.0
    • Fix Version/s: 5.12.0-b1
    • Component/s: Plugins
    • Labels:
      None

      Description

      People open tickets without a second thought of reading the documentation, or trying to find their answer elsewhere, and often it's an Emergency ticket.

      • Add 1 new "Visibility" option of "Client Only"
      • Add 2 new "Types" that include custom logic. "Checkbox Required", and "Escalate to Emergency". These are only available if "Client Only" is selected for Visibility.

      Checkbox Required

      Put the "Description" in an information box, which a checkbox below it that includes the "Label". The ticket cannot be opened unless they check the box (after hopefully reading the infobox description)

      Escalate to Emergency

      Similar to above, info box (alert box if possible) with the description input, and label for checkbox. However, checking the box will cause the ticket to be upgraded to an Emergency. This works best when "Emergency" is not an allowed priority for the department. So, to be clear, "Emergency" can be a status not allowed for the department, and this would effectively override that and make it an Emergency ticket.

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Description People open tickets without a second thought of reading the documentation, or trying to find their answer elsewhere, and often it's an Emergency ticket.

        - Add 1 new "Visibility" option of "Client Only"
        - Add 2 new "Types" that include custom logic. "Checkbox Required", and "Escalate to Emergency".

        *Checkbox Required*

        Put the "Description" in an information box, which a checkbox below it that includes the "Label". The ticket cannot be opened unless they check the box (after hopefully reading the infobox description)

        *Escalate to Emergency*

        Similar to above, info box (alert box if possible) with the description input, and label for checkbox. However, checking the box will cause the ticket to be upgraded to an Emergency. This works best when "Emergency" is not an allowed priority for the department.
        People open tickets without a second thought of reading the documentation, or trying to find their answer elsewhere, and often it's an Emergency ticket.

        - Add 1 new "Visibility" option of "Client Only"
        - Add 2 new "Types" that include custom logic. "Checkbox Required", and "Escalate to Emergency". These are only available if "Client Only" is selected for Visibility.

        *Checkbox Required*

        Put the "Description" in an information box, which a checkbox below it that includes the "Label". The ticket cannot be opened unless they check the box (after hopefully reading the infobox description)

        *Escalate to Emergency*

        Similar to above, info box (alert box if possible) with the description input, and label for checkbox. However, checking the box will cause the ticket to be upgraded to an Emergency. This works best when "Emergency" is not an allowed priority for the department.
        admin Paul Phillips made changes -
        Summary Support Manager: Add new custom field option required for opening the ticket Support Manager: Add new custom field options
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        admin Paul Phillips made changes -
        Description People open tickets without a second thought of reading the documentation, or trying to find their answer elsewhere, and often it's an Emergency ticket.

        - Add 1 new "Visibility" option of "Client Only"
        - Add 2 new "Types" that include custom logic. "Checkbox Required", and "Escalate to Emergency". These are only available if "Client Only" is selected for Visibility.

        *Checkbox Required*

        Put the "Description" in an information box, which a checkbox below it that includes the "Label". The ticket cannot be opened unless they check the box (after hopefully reading the infobox description)

        *Escalate to Emergency*

        Similar to above, info box (alert box if possible) with the description input, and label for checkbox. However, checking the box will cause the ticket to be upgraded to an Emergency. This works best when "Emergency" is not an allowed priority for the department.
        People open tickets without a second thought of reading the documentation, or trying to find their answer elsewhere, and often it's an Emergency ticket.

        - Add 1 new "Visibility" option of "Client Only"
        - Add 2 new "Types" that include custom logic. "Checkbox Required", and "Escalate to Emergency". These are only available if "Client Only" is selected for Visibility.

        *Checkbox Required*

        Put the "Description" in an information box, which a checkbox below it that includes the "Label". The ticket cannot be opened unless they check the box (after hopefully reading the infobox description)

        *Escalate to Emergency*

        Similar to above, info box (alert box if possible) with the description input, and label for checkbox. However, checking the box will cause the ticket to be upgraded to an Emergency. This works best when "Emergency" is not an allowed priority for the department. So, to be clear, "Emergency" can be a status not allowed for the department, and this would effectively override that and make it an Emergency ticket.
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.12.0 Sprint 3 [ 210 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked lower
        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours, 18 minutes [ 8280 ]
        Worklog Id 17652 [ 17652 ]
        abdy Abdy Franco made changes -
        Assignee Abdy Franco [ abdy ]
        abdy Abdy Franco made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        abdy Abdy Franco made changes -
        Time Spent 2 hours, 18 minutes [ 8280 ] 1 day, 2 hours, 13 minutes [ 36780 ]
        Worklog Id 17653 [ 17653 ]
        abdy Abdy Franco made changes -
        Time Spent 1 day, 2 hours, 13 minutes [ 36780 ] 2 days, 2 hours, 10 minutes [ 65400 ]
        Worklog Id 17654 [ 17654 ]
        abdy Abdy Franco made changes -
        Time Spent 2 days, 2 hours, 10 minutes [ 65400 ] 3 days, 2 hours, 10 minutes [ 94200 ]
        Worklog Id 17655 [ 17655 ]
        abdy Abdy Franco made changes -
        Time Spent 3 days, 2 hours, 10 minutes [ 94200 ] 4 days, 2 hours, 8 minutes [ 122880 ]
        Worklog Id 17656 [ 17656 ]
        abdy Abdy Franco made changes -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        jonathan Jonathan Reissmueller made changes -
        Story Points 3
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.12.0 Sprint 3 [ 210 ] 5.12.0 Sprint 3, 5.12.0 Sprint 4 [ 210, 214 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked lower
        abdy Abdy Franco made changes -
        Time Spent 4 days, 2 hours, 8 minutes [ 122880 ] 4 days, 2 hours, 32 minutes [ 124320 ]
        Worklog Id 17718 [ 17718 ]
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.12.0 Sprint 3, 5.12.0 Sprint 4 [ 210, 214 ] 5.12.0 Sprint 3, 5.12.0 Sprint 4, 5.12.0 Sprint 5 [ 210, 214, 215 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 4 days, 2 hours, 32 minutes
              4d 2h 32m

                Agile