Osticket: v1.10-dpr-6-g3e4b685 (3e4b685) - advanced search - zombie queues, still alive in 1.10.1

Created on 15 May 2015  路  14Comments  路  Source: osTicket/osTicket

I was wondering why some of my saved searches look weird and weren't usable or deleteable.
This occurs when you didn't name it before you save (had forgotten it). You can reproduce it when you do the following.

  1. Create a Search without a name:
    screenshot 1
  2. Close the window:
    screenshot 2
  3. Open the window again:
    screenshot 3
Search UI bug next

Most helpful comment

No I didn't tried it before. But I have just tested it and it behaves how you describe it:
null search

The saved search without a title isn't longer undeletable via the gui 馃憤
Thanks for the hint! The zombie is healed..

Should I close the issue report or wait until it is merged?

All 14 comments

@greezybacon has FAILED! ;)

@ntozier
Are you sure @greezybacon really failed?...
I mean this could be a feature and not a bug - or aren't there any easter eggs in osTicket?! :D

@Chefkeks I have clicked on them very excessive, no pong or other easter eggs were offered ;-) I think we could classify it as a undocumented way to create a styling bar..

@mfelber :D :+1:

You guys are cracking me up

hehehe. :)

DELETE FROM ost_queue WHERE title IS NULL; -- greezybacon has FAILED

I have just noticed that the zombies (undeletable & unusable saved searches) are still alive, even in 1.10.1 ;-)

Please put him out of his suffering..and give him a head shot!

I was under the impression that it was slated to be fixed in the next release. 1.11.

Have you guys tried this pull request? It'll still let you save with no name but it'll be NULL instead of blank. This way you can actually delete it later if it was an accident. Let me know how this goes! Cheers.

No I didn't tried it before. But I have just tested it and it behaves how you describe it:
null search

The saved search without a title isn't longer undeletable via the gui 馃憤
Thanks for the hint! The zombie is healed..

Should I close the issue report or wait until it is merged?

I would wait just in case other people run across this. :+1:

Ok, make sense.

Was this page helpful?
0 / 5 - 0 ratings