#Command Style Tickets inconsistency

1 messages · Page 1 of 1 (latest)

fresh cape
#

I will send a bug description after I take a break because of Wick

#

Description: The conflict happen when I use $new command. 2 tickets have the Command Style Tickets turned on and use the same monitor channel.

Steps to Reproduce: Turn on Command Style Tickets and set the same monitor channel in 2 tickets. Send $new command in monitor channel.

Expected Result: Show ticket list to choose and open the ticket

Actual Result: Only 1 of 2 tickets open, the another sends an error:

Warning: You're doing that too quickly, try again in 0s

#

(sorry for the short bug description, I don't have more energy to write the long bug description again)

#

and I don't know how to delete this post to re-post so I still use this post to report bug
If you wish to make a new post, I will do that, but please give me time to copy context from old post to new post, thanks!

half marlin
#

As far as I know ticket tool is supposed to only open the ticket for the panel that's the oldest. So Panel #1 will he prioritized before panel #2. But the error for the second panel is not supposed to show I think.

The expected result you gave is actually not the expected result, but it's still worth looking into

fresh cape
#

thanks! I don't know how to write expect results so I write it as a suggestion

unkempt urchin
# fresh cape

This issue was reported a time ago, although there isn't a complete fix the workaround to it is using threads to avoid having 2 panels monitoring the same channel.