Too many layers of bug reports

asked 2015-08-16 19:47:56 +0200

simo gravatar image

updated 2015-09-12 15:37:34 +0200

  • Jolla Sailor's internal bugzilla
  • maybe some platform for Jolla Tablet developer program
  • Early Access reports here
  • added by "normal users" reports here
  • external Mer bug tracker << added, thanks for comment @ossi1967

In the development point of view, and also in the communications point of view, this can't go on. Negative affects are already visible, looking at there are already 1706 unanswered bug reports on TJC, 20 of them marked as "tracked by Jolla". Users don't know if the rest are also reported elsewhere internally. TJC has been seen as not too good platform for bug reporting in general. My question is: What could we do to all these unanswered bug reports?

All of them: https://together.jolla.com/questions/scope:unanswered/sort:activity-desc/tags:bug/page:1/

Tracked: https://together.jolla.com/questions/scope:unanswered/sort:activity-desc/tags:bug/page:1/tracked:all/

edit retag flag offensive close delete

Comments

11

Personally, I would like to move all bug reporting to Bugzilla and leave TJC for general support and discussion. I guess it's possible to achieve by advertising somewhere near the text input field. Like, "looks like you try to report a bug, use Bugzilla instead." and a link to Bugzilla. The text analyzing heuristics must be pretty trivial.

ScumCoder ( 2015-08-16 21:12:04 +0200 )edit
1

Another bugtracker, instead of using TJC for that, has been requested, and here's a great discussion related to the issue. However, even after a new or opened bugtracker, we are still left with this huge amount of already existing reports here. This question focuses on what to do with these (link in the question), being more like a cleanup issue.

simo ( 2015-08-16 21:31:08 +0200 )edit
3

Ideally Jolla would/could have some QA guy/girl run through the bug tagged questions in TJC, test them and report them in the internal bugtracker if valid so the sailors can do their thing.

ApB ( 2015-08-17 00:59:27 +0200 )edit

@ApB Ain't that how it's done since the bug report number one? (At least I'd suppose so, otherwise no idea at all in the whole reporting)

simo ( 2015-08-17 01:05:59 +0200 )edit
4

@simo

I have the feeling that sailors -the ones that check TJC- only test/read their respective area bugs and report it internally. I don't think there is a single person that handles it all -in addition to the sailors that frequent TJC-. And in this case if a dev doesn't frequent TJC the bug will not be reported internally soon. Big bugs of course affect many people and those (sailors) who have them will report them -i suspect- but not everyone has the same usecases for their phones. A bug that i see might not be seen by a dev that uses the phone differently.

ApB ( 2015-08-17 01:16:46 +0200 )edit