This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Request for separate Bug Report "subforum"

We have separate "subforums" for 

'Eos Family Consoles > Eos Family'

'Eos Family Consoles > Eos Family Feature Requests'

'Eos Family Consoles > Fixture Requests - Eos Family' 

'Eos Family Consoles > Eos Family Show Control Support (MIDI, SMPTE, OSC, RTC, etc)

 

I think we should also have a separate "subforum" for

'Eos Family Consoles > Eos Family - Bug Reports'

In the Eos Open Beta forums we already have this distinction

'Eos 3.3.0 Open Beta > Eos 3.3.0 Open Beta Bug Report'

But I am not running on a Beta version, so I would think that is not the place for bug reports in non-Beta versions

Currently it feels like some of my bug reports get lost among the questions and discussions of the main 'Eos Family' "subforum"

I do not expect fixes or solutions for every bug I report, but when it has been 4 months and there are 0 replies on a bug report I made, it feels like it hasn't even been read. Replies such as "Thank you for reaching out. This is now written up as [EOS-57303]." showing it has at least been read and logged would be appreciated

Thank you,

Steven




[locked by: Nick.Gonsman at 6:19 PM (GMT -5) on Thu, Aug 21 2025]
Parents
  • Hi Steven - the "Eos Family" section is for bug reports, so please continue to post there. And indeed, we can always be doing better about following up on posts. Sometimes the team has to consult with R&D, or validate the bug before writing it up, or they are busier with other real-time tasks like running our phone lines and email accounts.

    I do watch the forums, and our support team brings critical or frequently encountered bugs to my attention. But between the forums, phone support, email, social media, and a global presence, we hear from thousands of people monthly - and our first mission is to keep shows online. Bugs, once they can be reproduced in-house and written up, get submitted to R&D and prioritized alongside other bugs, critical issues, new features, and other development considerations.

    I'll continue to explore with our management teams how we can improve response to reports we receive which aren't real-time critical, and as such can get left languishing. In the meantime, continue to post - nothing goes away until we deal with it, and we will continue doing our best to keep up with the posts. 

    Nick Gonsman, Eos Family Product Manager

Reply
  • Hi Steven - the "Eos Family" section is for bug reports, so please continue to post there. And indeed, we can always be doing better about following up on posts. Sometimes the team has to consult with R&D, or validate the bug before writing it up, or they are busier with other real-time tasks like running our phone lines and email accounts.

    I do watch the forums, and our support team brings critical or frequently encountered bugs to my attention. But between the forums, phone support, email, social media, and a global presence, we hear from thousands of people monthly - and our first mission is to keep shows online. Bugs, once they can be reproduced in-house and written up, get submitted to R&D and prioritized alongside other bugs, critical issues, new features, and other development considerations.

    I'll continue to explore with our management teams how we can improve response to reports we receive which aren't real-time critical, and as such can get left languishing. In the meantime, continue to post - nothing goes away until we deal with it, and we will continue doing our best to keep up with the posts. 

    Nick Gonsman, Eos Family Product Manager

Children
Related