Klever

Evgeny Novikov wrote:

You implemented this as an option, but I asked Pavel to provide a feedback. I guess that having a help message will be better.

Can't do help message popup on automatically updated part of job page (everything unsader the "view" bar).

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

You implemented this as an option, but I asked Pavel to provide a feedback. I guess that having a help message will be better.

Can't do help message popup on automatically updated part of job page (everything unsader the "view" bar).

So, I am wondering how did you implement "?" for consumed computational resources.

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

You implemented this as an option, but I asked Pavel to provide a feedback. I guess that having a help message will be better.

Can't do help message popup on automatically updated part of job page (everything unsader the "view" bar).

So, I am wondering how did you implement "?" for consumed computational resources.

Before updating I hide this popup in javascript, then update data, then initialize popup, then if it was shown before update I show it again. For verdicts I have to set unique id for each popup to know which one show be shown after update. Set of verdicts is not fixed, it is too complicated to handle with it.

The idea was, that unprepared user does not confirm all unsafes after relaunch the job. Not to confuse him with zero numbers (confirmed bugs), we should show that most of marks are applied. Anyway, in job tree all bugs (not confirmed) are shown. And at job page the same number is hidden into braces. A user should see equal number of bugs both on job tree page and at job page, so, I suggested to hide the detailed information (about confirmed unsafes).

A help message may be useful, but it is likely a secondary feature.

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

You implemented this as an option, but I asked Pavel to provide a feedback. I guess that having a help message will be better.

Can't do help message popup on automatically updated part of job page (everything unsader the "view" bar).

So, I am wondering how did you implement "?" for consumed computational resources.

Before updating I hide this popup in javascript, then update data, then initialize popup, then if it was shown before update I show it again. For verdicts I have to set unique id for each popup to know which one show be shown after update. Set of verdicts is not fixed, it is too complicated to handle with it.

Perhaps it would be better to send such the popups each time when updating pages. Another solution is to store help messages in immutable places, e.g. static help pages and just reference them.

Pavel Andrianov wrote:

The idea was, that unprepared user does not confirm all unsafes after relaunch the job. Not to confuse him with zero numbers (confirmed bugs), we should show that most of marks are applied. Anyway, in job tree all bugs (not confirmed) are shown. And at job page the same number is hidden into braces. A user should see equal number of bugs both on job tree page and at job page, so, I suggested to hide the detailed information (about confirmed unsafes).

This isn't the "unprepared" user - this is the lazy user. And I insist to "confuse" such the users with different numbers, so, nobody will think about them as heroes. Who prevents lazy users to rely upon numbers in braces?.. Help messages will guide them to do this or to do all the best.

I agree that we missed the number of confirmed bugs, false alarms, etc. at the jobs tree page.

This isn't the "unprepared" user - this is the lazy user.

Users always want as much automation as possible. At the same time users want as simple representation as possible, because overflowing information misleads the user.
The confirmation mechanism is not demanded by some users. In such case I would prefer an option to hide it.

Vladimir Gratinskiy wrote:

Implemented in branch "feature_8336".

The number of confirmed unsafes is also shown at the unsafes list page and, maybe, somewhere else. Did you enhance corresponding views as well?

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

Implemented in branch "feature_8336".

The number of confirmed unsafes is also shown at the unsafes list page and, maybe, somewhere else. Did you enhance corresponding views as well?

Fixed.