|
Comment by
Robin Shen
[
28/Jun/10 11:42 PM
]
|
|
Do you mean the dashboard page showing all configurations. The inherited value is not shown there since it might take a lot of time to calculate inherited settings for all configurations in the tree.
|
|
Comment by
Roger Perkins
[
29/Jun/10 09:21 AM
]
|
|
Yeah, I did mean the dashboard. I can see why you wouldn't want to try and show them in that case, is it not possible to cache the inherited values in the configurations to make it fast to display them? Having the queue/schedule field on dashboard screen just filled with "inherited value" isn't really adding much other than noise to that screen (certainly not close to the same value as showing inherited values of variables on that screen, very nice to have now)
|
|
Comment by
Robin Shen
[
30/Jun/10 08:03 AM
]
|
Caching this inherited information means once a configuration is updated, all descendant configurations need to be updated since their inherited setting might be affected, and this cause changing schedule setting of a configuration noticeably slower if the tree is big.
Another problem is that when schedule of parent configuration is paused/resumed, schedule status of all descendant configurations also need to be updated via ajax to reflect the actual inherited schedule status, which is difficult to implement in current design.
To avoid noise on the screen, "inherited from parent" information is grayed.
|
Generated at Fri Oct 03 22:37:38 UTC 2025 using JIRA 189.
