Where's the bug list?

, ,
1

Imported from previous forum

2

I have raised 21 bugs by email.  I've included browser version, OS version and screenshots.

Where is the complete list of bugs so I can avoid wasting my time raising a bug someone else has already found?

 

3

Hi John,

We will certainly be discussing this with the team at FPL.

We have an internal mechanism for bug tracking which we share directly with the Program Office, and where we are made aware of issues, we are addressing them through this method. However, we are not contracted to provide front-line support on the website generally, so the FPL team will need to make a decision about how they wish to manage bug-tracking and reporting in relation to the user base as a seperate process.

Daniella, the project lead, is out of the office until Wednesday but we will be raising this as a priority with her as soon as she returns.

Jacob

4

Nothing happened on this....

5

We supply a real-time Bug List to the Programme Office via JIRA, (also tracking feature requests, content changes, config changes, preferences etc., which do not constitute Bugs). This is formally reviewed and prioritised on a scheduled basis.

Prioritisation of Bugs (and also relative priority of feature requests and changes) is directed by the Programme Office

Communication of this list to reporting users is via the Programme Office.

Of the 43 Bugs reported to date, 22 are resolved, and 21 outstanding.

Several of the related larger/high priority ones relating to Browser Compatibility and 500 errors arising from time-out issues (due to very large number of bespoke notifications being generated before browser context is surrendered on "post" event) are currently in test and aniticipated to be pushed to production once they have been fully evaluated, which should be in the next few days. Several other related items such as the ability to "save without notifying" and some other protections against duplicate notifications will be done at the same time, since their resolution involved the same system components and it made senses to address them in the same work item.

 

 

6

Corrected the previous post- 43 was total Bugs, not Closed, which should have been 22.

There are also Feature Requests, Config Changes, Improvements, etc which are not defects, but are prioritised in the same excercise, and because of importance / impact may be assigned higher priority.