I don't really have much use for a delete button on the list of tickets, but I would really like a one-button close for a ticket. This would save several clicks and speed up the process of managing my tickets. It also helps preserve data.

For extra bonus points, maybe it would be a delete button only when the filter included closed tickets and a close button all other times.

Perhaps their is a deeper project management reason to prefer the delete. If so, I'll bow to the explanation and close this ticket.

Comments

mikepadiernos’s picture

mikepadiernos commented

I think this valid. It would make it easier to have a close for posterity. Plus, if there's updates on one of the tickets it could be reopened.

andrewjohns’s picture

andrewjohns commented

I sort of agree with this. How I'd probably prefer it to work is that deleting just flags the ticket up as hidden to certain users, but those with rights can still search on them. This enables the standard users to "delete" tickets from their list to keep it clean, but the content is still searchable by admins if a similar issue crops up again.

Magnity’s picture

Magnity commented
Component: User interface » Storm Ticket
Status: Active » Closed (won't fix)

There is a permission to control who can delete tickets.

I would suggest the way to do this is to have a status called 'closed'? This could be done by using attributes.