w.Intercom = i;Change this board to differentiate between actual bugs and actual enhancement requirements — tado° Community

Change this board to differentiate between actual bugs and actual enhancement requirements

policywonk
policywonk ✭✭✭
in Suggestions, Ideas and Improvements

Am getting increasingly concerned that this community board does not differentiate between actual bugs in Tado systems and enhancement requirements.

As an example @davidyall recently identified a bug, unequivocally, in the way in which schedules are organised and what happens when there is a manual override.

It is possible to differentiate between actual bugs, complaints and enhancements - and it should be.

Here's the proposal.

  1. Create a community driven bug list on this Board. Every time is given a monthly status report of:
    1. Initially Reported,
    2. Then Accepted/Refused
    3. Then either Pending/ Addressed/Dropped
    4. Then Closed.
  2. Only allow Admins and moderators to file/update this list.
  3. Allow Admins/moderators to review the enquiries filed by users and, if they are clearly based upon a perceived bug, forward the case to the bug board, which gives the tech team and support team room to comment;
  4. Or if they are really an enhancement, to forward to the enhancement request board. This reduces the enhancement request list to less of an impression of Disneyland.
  5. Enable Tado tech to decide upon the status of each request in the Enhancement Request board and/or Bug notice board.

This may not be politically soft on users or Tado tech support, but it will enable us all to be clear about gaps, what we know is possible or critical, what is not worth waiting for.

Would appreciate it @Emcee @Rob @davidlyall, @wateroakley would consider.

2
Up
2 votes

Active · Last Updated

Comments

  • davidlyall
    davidlyall ✭✭✭

    Sounds like a good idea.

    Unfortunately, the line has been blurred between these items for a long time. It would also probably make some sense to make an initial list of common enhancement requests and bugs then archive off this forum so that a fresh start could be made

  • policywonk
    policywonk ✭✭✭

    @Davidlyall. Completely agree. It would also help to create another category, in which established effective procedures to implement a boiler/thermostat combination are well documented.

    For example, in the last 3 years there have been dozens of enquiries about the use of HT-BUS, E-BUS - digital comms links with boilers - and their implementation. It is clear that the Tado team are stressed and cannot always give unequivocal recommendations. But it is possible for end users to document what they did that worked so that we can search and apply lessons learned elsewhere.

Categories