Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a way to configure which day is first day of the week #21

Open
psiroky opened this issue Jun 11, 2013 · 6 comments
Open

Provide a way to configure which day is first day of the week #21

psiroky opened this issue Jun 11, 2013 · 6 comments

Comments

@psiroky
Copy link
Contributor

psiroky commented Jun 11, 2013

Currently the default behavior is that week starts with Monday. We should provide a way for users to configure which day is first day of the week.

The first day could be also (by default) determined from user's locale settings.

@triceo
Copy link

triceo commented Jun 11, 2013

Where do we make that configuration? On the server level - as a servlet param, for example? Or at the user level, in the web app somewhere? My $0.02 would be to just trust the locale.

@psiroky
Copy link
Contributor Author

psiroky commented Jun 11, 2013

I think the best would be to use the locale by default, but also allow users to override that (in GUI) if they choose to, e.g. the user has en_us locale in browser, but wants to see the week staring with Monday.

@salaboy
Copy link
Contributor

salaboy commented Jun 11, 2013

If we trust the locale we will need to show it somewhere, and allow the user to override it. We need to think in a configuration/administration section for all these stuff.

@manstis
Copy link
Member

manstis commented Jun 11, 2013

Persistent, user defined variable configuration should be stored in
system.git using the ConfigurationService.

This doesn't rule out use of web.xml for more static configurations.. but
no properties files.

On 11 June 2013 19:30, Salaboy [email protected] wrote:

If we trust the locale we will need to show it somewhere, and allow the
user to override it. We need to think in a configuration/administration
section for all these stuff.


Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-19282727
.

@salaboy
Copy link
Contributor

salaboy commented Jun 11, 2013

Definitely @manstis is there anyone in charge of creating a set of UI to handle that information stored in that ConfigurationService? because it sounds as a good community contribution :)

@manstis
Copy link
Member

manstis commented Jun 11, 2013

Nobody is doing any UI for it at the moment.

On 11 June 2013 21:18, Salaboy [email protected] wrote:

Definitely @manstis https://github.com/manstis is there anyone in
charge of creating a set of UI to handle that information stored in that
ConfigurationService? because it sounds as a good community contribution :)


Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-19289302
.

nmirasch pushed a commit to nmirasch/jbpm-console-ng that referenced this issue Jun 22, 2016
Hide selector when only one template is available
nmirasch added a commit to nmirasch/jbpm-console-ng that referenced this issue Mar 6, 2018
cristianonicolai added a commit that referenced this issue Mar 16, 2018
…PM-6659, JBPM-6660 - Runtime views update, new Manage section (#994)

* JBPM-6802:Add breadcrumbs to list and details views

* Update Breadcrumb i18n keys

* Use definition name instead of deployment id for breadcrumb

* JBPM-6803: Migrate server template selector to breadcrumb area.

* Migrate runtime views to new perspective layout

* Move detail screens to full screen

* Review toolbar primary action buttons

* Review master detail API (#12)

Remove table style for selected row
Remove place status handling for opening details screen

* Add new filters dock panel (#10)

* JBPM-6826:Include Manage selector ( Inventory Switcher ) (#11)

* Update attribute selector label to Filter By (#15)

* Remove user task list from manage section (#14)

* Add new saved filters dock panel (#9)

* JBPM-6877 - Fix screen id for navigating to task and process instance details screens (#16)

* [AF-913]: Added Category to resource type and integrated with UX/UI (#966) (#18)

[AF-913]: Added Category to resource type

* JBPM-6846: Move process model to detail tab (#13)

* JBPM-6887 - Rename Task Lists to Task Inbox (#986) (#19)

* JBPM-6892 - Remove spacing between table results and controls (#988) (#22)

* JBPM-6841: Review details page layout. Details alignment, input fields size, primary button review and task context tab removed (#20)

* JBPM-6867 - Restyle manage view table (#17)

* JBPM-6885 - Split Task & Process Dashboard tabs into separated screens (#987) (#23)

* JBPM-6867 - Layout updates to manage result list (#24)

- Fix scrolling
- Remove table rows stripes
- Add grey background to table header

* JBPM-6879: Prepend "Manage" to all runtime management list views breadcrumb (#25)

* error detail breadcrumb updated with the error detail title (#21)

* Upgrade supported WildFly version to 11. (#983) (#26)

* Upgrade supported WildFly version to 11.

This reverts commit 1d8f778.

* Clean up auth properties files comments

* fixed server logging in GWT SDM

* JBPM-6174: Add error count column to the task admin list (#965) (#27)

* JBPM-6825 - Move saved and quick filters to docks (#28)

* JBPM-6881 : Rename Task Administration menu to Tasks (#30)

* JBPM-6879: Prepend "Manage" to all runtime management list views breadcrumb. Process definition breadcrumb from new instance (#31)

* JBPM-6841: Review details page layout. Spacing between tab header and content (#32)

* JBPM-6886 : Update Dashboards layout (#29)

* JBPM-7002 - Group action buttons in list table to kebab (#33)

* Enhance filters tests (#34)

* JBPM-6894 - User should be able to define case, process, activity level SLA (#990) (#36)

* JBPM-6793 - Remove onclick and onmouseover in process diagram svg content (#37)

* Increase space between tab and content in task admin and assignment tabs (#39)

* Test addition: Breadcrumbs and ManageSelector (#38)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants