Project

General

Profile

Feature #8346

Forcibly update job pages when job decision statuses change

Added by Evgeny Novikov about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
-
Start date:
08/14/2017
Due date:
08/14/2017
% Done:

100%

Estimated time:
Published in build:

Description

Now job pages aren't automatically updated after some time. This helps to considerably reduce a server load while it almost always has sense since users don't see on these pages during long times.

Unfortunately job pages aren't updated even after job decision statuses change. As one of consequences users can see confusing error messages for some actions, e.g. there is a related separate issue #8345.

I suppose that after some period of time you can exchange with a server just a job decision status and update the job page if it changes. Since retrieving and sending this status isn't so resource intensive as for other updated information it won't cause a huge server load.


Related issues

Related to Klever - Bug #8345: Incorrect error message when canceling job decisions after page updates are switched offNew08/14/2017

Actions

History

#1

Updated by Evgeny Novikov about 3 years ago

  • Priority changed from High to Urgent

This is quite useful feature.

#2

Updated by Vladimir Gratinskiy about 3 years ago

  • Due date set to 08/14/2017
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Implemented in "feature_8346".

#3

Updated by Evgeny Novikov about 3 years ago

  • Status changed from Resolved to Closed

I tested that it works and merged the branch to master in 3b1e037e. Statistics says that getting just job decision statuses takes an order less time than getting all the data even for a very simple job (for complicated jobs there will be the several orders difference).

Also available in: Atom PDF