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

Support Manager: Allow tickets to be permanently deleted.

        Details

        • Type: Story
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.4.0
        • Fix Version/s: 4.3.0-b1
        • Component/s: Plugins
        • Labels:
          None

          Description

          • People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

          Allow tickets to be changed to be changed to a status of "deleted". Then, when cron runs, delete any tickets that are in this status and have no updates during the past 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

          Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet. When deleted, they are not recoverable. Everything to do with that ticket should be deleted from the database.

          This delay allows tickets accidentally trashed to be recovered within that period of time.

          This should also be a bulk edit action.

            Activity

            Ascending order - Click to sort in descending order
            admin Paul Phillips created issue -
            admin Paul Phillips made changes -
            Field Original Value New Value
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            2. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.
            admin Paul Phillips made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.
            admin Paul Phillips made changes -
            Rank Ranked higher
            admin Paul Phillips made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to a status of deleted. Then, when cron runs, delete any tickets that are in this status and have no updates for 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet.

            This delay allows tickets accidentally deleted to be undeleted within that period of time.
            admin Paul Phillips made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.

            2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.

            3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to a status of deleted. Then, when cron runs, delete any tickets that are in this status and have no updates for 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet.

            This delay allows tickets accidentally deleted to be undeleted within that period of time.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.-

            -2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.-

            -3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to a status of deleted. Then, when cron runs, delete any tickets that are in this status and have no updates for 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet.

            This delay allows tickets accidentally deleted to be undeleted within that period of time.
            admin Paul Phillips made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.-

            -2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.-

            -3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to a status of deleted. Then, when cron runs, delete any tickets that are in this status and have no updates for 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet.

            This delay allows tickets accidentally deleted to be undeleted within that period of time.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.-

            -2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.-

            -3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to a status of deleted. Then, when cron runs, delete any tickets that are in this status and have no updates for 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet.

            This delay allows tickets accidentally deleted to be undeleted within that period of time.

            This should also be a bulk edit action.
            admin Paul Phillips made changes -
            Assignee Tyson Phillips [ tyson ]
            admin Paul Phillips made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.-

            -2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.-

            -3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to a status of deleted. Then, when cron runs, delete any tickets that are in this status and have no updates for 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet.

            This delay allows tickets accidentally deleted to be undeleted within that period of time.

            This should also be a bulk edit action.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.-

            -2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.-

            -3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to be changed to a status of "Trash". Then, when cron runs, delete any tickets that are in this status and have no updates during the past 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet. When deleted, they are not recoverable. Everything to do with that ticket should be deleted from the database.

            This delay allows tickets accidentally trashed to be recovered within that period of time.

            This should also be a bulk edit action.
            admin Paul Phillips made changes -
            Fix Version/s Short Term [ 10800 ]
            admin Paul Phillips made changes -
            Rank Ranked higher
            tyson Tyson Phillips (Inactive) made changes -
            Rank Ranked lower
            jonathan Jonathan Reissmueller made changes -
            Sprint 4.3.0 Sprint 1 [ 49 ]
            jonathan Jonathan Reissmueller made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            -1. Create a new "Trash Bin", and the ability for staff who have access to a department to send tickets here.-

            -2. Add a new Support Staff permission for access to the Trash Bin. This will allow designated Staff access to view and permanently delete tickets in the bin that belong to departments for which they have access.-

            -3. Add a new "Trash Bin" section, where tickets sent here can be viewed. All of their original data, including the department assignment and replies will be preserved. Staff with access to this section can perform one of 2 actions on tickets here. Restore, or Delete. Allow multi-select of tickets similar to the ticket overview, and use the same action box that appears in the bottom right as for other actions.-

            Allow tickets to be changed to be changed to a status of "Trash". Then, when cron runs, delete any tickets that are in this status and have no updates during the past 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet. When deleted, they are not recoverable. Everything to do with that ticket should be deleted from the database.

            This delay allows tickets accidentally trashed to be recovered within that period of time.

            This should also be a bulk edit action.             		People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            Allow tickets to be changed to be changed to a status of "Trash". Then, when cron runs, delete any tickets that are in this status and have no updates during the past 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet. When deleted, they are not recoverable. Everything to do with that ticket should be deleted from the database.

            This delay allows tickets accidentally trashed to be recovered within that period of time.

            This should also be a bulk edit action.
            jonathan Jonathan Reissmueller made changes -
            Description People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            Allow tickets to be changed to be changed to a status of "Trash". Then, when cron runs, delete any tickets that are in this status and have no updates during the past 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet. When deleted, they are not recoverable. Everything to do with that ticket should be deleted from the database.

            This delay allows tickets accidentally trashed to be recovered within that period of time.

            This should also be a bulk edit action.             		* People accepting tickets from non-clients by email or web, often receive spam tickets. Generally we like to hold onto data, but there is a legitimate need to delete spam tickets.

            Allow tickets to be changed to be changed to a status of "deleted". Then, when cron runs, delete any tickets that are in this status and have no updates during the past 24hrs. When changing the status of the ticket, the status change should be visible in the ticket, and this should be counted as an update when determining whether it's been 24hrs.

            Tickets with a status of deleted should be able to be changed back to another status so long as they haven't been processed for deletion yet. When deleted, they are not recoverable. Everything to do with that ticket should be deleted from the database.

            This delay allows tickets accidentally trashed to be recovered within that period of time.

            This should also be a bulk edit action.
            jonathan Jonathan Reissmueller made changes -
            Assignee Jonathan Reissmueller [ jonathan ]
            Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
            Status Open [ 1 ] In Progress [ 3 ]
            jonathan Jonathan Reissmueller made changes -
            Remaining Estimate 0 minutes [ 0 ]
            Time Spent 5 hours, 27 minutes [ 19620 ]
            Worklog Id 10626 [ 10626 ]
            jonathan Jonathan Reissmueller made changes -
            Time Spent 5 hours, 27 minutes [ 19620 ] 5 hours, 47 minutes [ 20820 ]
            Worklog Id 10626 [ 10626 ]
            Automated transition triggered when Jonathan Reissmueller created pull request #22 in Stash -
            Status In Progress [ 3 ] In Review [ 5 ]
            Resolution Fixed [ 1 ]
            jonathan Jonathan Reissmueller made changes -
            Time Spent 5 hours, 47 minutes [ 20820 ] 7 hours [ 25200 ]
            Worklog Id 10631 [ 10631 ]
            Automated transition triggered when Tyson Phillips (Inactive) merged pull request #22 in Stash -
            Status In Review [ 5 ] Closed [ 6 ]
            tyson Tyson Phillips (Inactive) made changes -
            Sprint 4.3.0 Sprint 1 [ 49 ]
            tyson Tyson Phillips (Inactive) made changes -
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            tyson Tyson Phillips (Inactive) made changes -
            Fix Version/s 4.3.0-b1 [ 11019 ]
            tyson Tyson Phillips (Inactive) made changes -
            Fix Version/s Short Term [ 10800 ]
            tyson Tyson Phillips (Inactive) made changes -
            Issue Type New Feature [ 2 ] Story [ 7 ]
            tyson Tyson Phillips (Inactive) made changes -
            Story Points 5
            tyson Tyson Phillips (Inactive) made changes -
            Sprint 4.3.0 Sprint 1 [ 49 ]
            tyson Tyson Phillips (Inactive) made changes -
            Rank Ranked lower
            jonathan Jonathan Reissmueller made changes -
            Status Reopened [ 4 ] Closed [ 6 ]
            Resolution Fixed [ 1 ]
            jonathan Jonathan Reissmueller made changes -
            Sprint 4.3.0 Sprint 1 [ 49 ]

              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:
                  15/Jun/18

                  Time Tracking

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