can't see that Jolla is investigating a specific bug any more?

asked 2016-09-10 08:54:29 +0300

shining gravatar image

after an update I got an overnight battery drain of ~10% in flight mode. So I hit tjc and found a bug report right away. I followed the "question" and some users made great efforts to investigate this bug. At some point a user chris.adams got involved and I found out in another question, that he has a jolla.com mail address. So is he a developer at Jolla? I guess, but I don't know for sure. I remember a time, when a bug report in tjc got flagged when Jolla had this bug under investigation and is working on a fix. Nowadays there is no indication that Jolla will put some efforts to it and for me it is a kind of rude behaviour towards the user who uncovered and reported the bug and to the community itself. It can't be that hard to show on tjc, that an issue is assigned to someone.

Just my 2 cents

edit retag flag offensive close delete

Comments

3

Yes, some indication that something is confirmed by Jolla as a bug is highly desirable. Some tags - confirmed, needs-confirmation, target release, etc - which are only set by Jolla perhaps. I notice some are marked 'tracked by Jolla' or something similar - which rather implies that others are not.

A proper bug tracker would be better of course, but that's been shouted down often enough.

DaveRo ( 2016-09-10 11:21:45 +0300 )edit

Yes, Chris Adams is one of the developers at Jolla, dealing with UI and middleware components.

Spam Hunter ( 2016-09-12 00:35:42 +0300 )edit
1

Together isn't really a good place to fill a bug.

You should fill in through bugzilla for SailfishOS

or you should mail Jolla through care(care@jolla.com).

BonoNL ( 2016-09-12 00:36:01 +0300 )edit

@BonoNL I'd use mer-bugzilla if I knew it were a Mer issue. But they mostly seem to be Jolla's responsibility. For example this media tracker bug. That's crying out for a proper bugzilla entry, with some Jolla direction and input, (confirmed, priority, needsinfo etc). What if anything is happening? (It no longer affects me after I've altered my ID3 tags but it's a major bug IMO.)

Or my minor MTP bug. It's been confirmed, I think. Just an 'acknowledged by Jolla' and 'priority low' would be nice. If I get no reaction I'll stop bothering to report it.

DaveRo ( 2016-09-12 08:18:58 +0300 )edit
2

I commented at various times in that other TJC report about the issue, linked to two separate bug fixes, mentioned the internal bug numbers which were tracking the issue, and said the update version number in which the fix can be expected... Furthermore, I communicated via email with the (extremely helpful and responsive) user who was investigating the bug, who was able to provide me with extra information (including logs) which I needed to track down the root cause of the issue.

You're right, there is some way to set a "tracked by Jolla" flag - but I am not a TJC admin, so I'm not sure how to do that.

chris.adams ( 2016-09-13 10:01:07 +0300 )edit