Symbol white

← Back to other Sirportly suggestions

redirect after merging tickets

4ab1d46a9e06f18b95c0c4525264edfe?rating=pg&size=52&default=mm
suggested by Stefan N
29

After tickets are merged the old ticket id becomes inactive. Currently this results in a 404 - Not Found error when accessing the old page of the ticket. 
I think it would be much better if the page would do a 301 HTTP redirect to the ticket with the ID it was merged with. 
 
This should be a very quick fix. 
 
 
Our use-case where the current behaviour hurts very much is this: 

We have macros which send out notifications to our staff when a private note is added and the email includes a direct link to the staff interface. 
So now when a ticket is merged after a private note is added this direct link results in a 404. Then it becomes hard to find the new ticket…

Complete We've implemented this suggestion!

Comments (6)

  • +1 for this idea.

    posted by Unknown User
  • Yeah, it would be very useful - there are all sorts of ways both customers and staff can end up with an old ticket number which no longer exists after merging.
     
    Also, I'm always in favour of anything which improves the audit trail.

    43535555a26ae0a9aacc5c6af1d79794?rating=pg&size=52&default=mm
    posted by Edward D
  • Also just from a purely architectural perspective (HTTP) this is the right way to handle content which moved somewhere else

    4ab1d46a9e06f18b95c0c4525264edfe?rating=pg&size=52&default=mm
    posted by Stefan N
  • Good idea. +1

    1da1ef6ab4c3ac4f9be41611befa5d4f?rating=pg&size=52&default=mm
    posted by Ryan D
  • The lacking of this feature is still a daily annoyance for us and it seems to be such a quick fix.

    Are you considering working on this?

    4ab1d46a9e06f18b95c0c4525264edfe?rating=pg&size=52&default=mm
    posted by Stefan N
  • +1

    48efb73611422977e63549a180a951c0?rating=pg&size=52&default=mm
    posted by Scott T