Hide Forgot
Created attachment 836042 [details] This shows it breaking... Description of problem: Workspace can only be created as long as there is at least Translation for English for the Workspace name. I set the language of my Dashbuilder to Portuguese and tried to create a new Workspace, only with the name in Portuguese, and I could not. I then went and set the name for English and Portuguese and it worked. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Open Dashbuilder 2.Set Language to Portuguese 3.Go to workspace Manager/creator (http://localhost:8080/dashbuilder/Controller?_fb=tsch&_fp=NewWorkspace&csrf=40702697) 4.Try creating workspace with a name only for portuguese. 5.There's an error "It was not possible to create the workspace. The name of the workspace should be at least in the default language. The title of the workspace should be at least in the default language." Actual results: Expected results: You should be able to create workspaces and other assets on any language, not ALWAYS english and something else. Additional info:
To clarify the problem, it's simply that by convention it's always mandatory to enter a page description or title in the default installation language (English), to provide a fallback in case a given translation is not present. We can change this check.
We have removed this restriction and now it's possible to create a new workspace, or page in any language. It's also worth to mention that the system will always try to display the name for the current user language but, if not found, it'll get the name defined regardless the language used. Github commit (master): https://github.com/droolsjbpm/dashboard-builder/commit/51ab935ed97b945b4ef7b0e1f975d4611b0ab552
Please, set to modified only after cherry-pick to 6.0.X
Cherry-picked from master and pushed to the 6.0.x branch. Github commit (6.0.x): https://github.com/droolsjbpm/dashboard-builder/commit/73e634b04ad91f729f740a0160308d7d6a13acc0
Verified on 6.0.1.ER1. It's possible to create a new workspace in all default languages.
Locale-specific issues are only tested manually by QA. Adding support for testing them to our automated UI-testing frameworks would require disproportionate development effort with little to show for it.