-
Improvement
-
Resolution: Won't Fix
-
Trivial
-
None
I want a feature to delete the user setting of trend graph of CheckStyle or Findbugs preserved in the cookie.
When the graph is set on a configuration screen where it can go from the link on a configuration screen of the job, it is preserved in the text file on the server.
However, when configuration in the graph is done on the configuration screen where it can go from the link under the graph on the job screen, this setting is preserved in the cookie of a client browser.
The setting of the server is not reflected until the cookie of a client browser is deleted when preserving it in the cookie once. With this, I think that a set text file in the server is meaningless.
I want you to add the feature to delete the cookie concerning the graph setting on the Web screen of hudson.
- is related to
-
JENKINS-14185 Provide global configuration of settings
-
- Resolved
-
[JENKINS-7443] Feature to delete the user setting of trend graph preserved in the cookie.
iijimas
added a comment - I think that I can easily achieve it if the function to reset the setting of the graph of a browser of each client in the value of default is provided to see the graph similarly in two or more members in the team.
When each member sets it to the browser cookie under the present situation, the settings cannot be united in each client environment.
iijimas
added a comment - I think that I can easily achieve it if the function to reset the setting of the graph of a browser of each client in the value of default is provided to see the graph similarly in two or more members in the team.
When each member sets it to the browser cookie under the present situation, the settings cannot be united in each client environment. Sorry, I'm not sure if I understand correctly. Adding a reset link will only unify the graphs if all users actually use that link and don't configure the graphs on their own.
So this requirement still needs to be refined! What would you like to achieve? That all users see the same graphs? That users don't change the graphs that are specified in the project?
Well, the idea behind that configuration is simple: the server configuration provides default values for the graph. These values will be used if the user does not change the graph configuration in the browser. If the user would like to use a different configuration then these values are stored in the cookie (per user). From that moment on, the user will never use the server configuration anymore.
What is the reason that you would like to re-use the server configuration rather than the current user configuration?