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

Default configuration for entire organisation #20

Open
RoyVisserOF opened this issue Mar 16, 2018 · 5 comments
Open

Default configuration for entire organisation #20

RoyVisserOF opened this issue Mar 16, 2018 · 5 comments

Comments

@RoyVisserOF
Copy link

Is it somehow possible to specify a default configuration (fields and order to print for each work item type) for the entire organization? Maybe we couldn't find it or it is not available?

The configuration for each user is great to overrule a default configuration, but now all our 200+ users must first specify which fields they want to print for each work item.

Kind regards,
Roy

@MrTarantula
Copy link
Owner

I can probably do this by adding a Hub in the Admin settings, here:

image

Would it be better to have a configuration per project, or per organization?

@MrTarantula
Copy link
Owner

I guess I could explain what the hub would be. It would look exactly like the other Work Item Print Hub, but with some text showing that configuring it here will set the default for the project/organization. The idea would be that if a user doesn't have it configured, they will get the default, but if they make any changes in the normal hub, then their custom settings would be saved for only them. Does that seem reasonable?

@RoyVisserOF
Copy link
Author

Your last suggestion would be great. For us it is not a problem if specific users makes overrules for themselves, but in the current situation every user starts with a blank template and I'm afraid the majority will not update these settings but won't user the print option. anymore A default for the project/organization would definitily solve this.

In our situation, a default on the collection level would be the best, but specifying the settings on a project level is also ok (we have about 10 projects in one collection)

@MrTarantula
Copy link
Owner

On second thought, collection-level settings may be a problem. Within a collection you may have projects using different process templates. I suppose I could add a field to select the process templates, and set the defaults per template. That adds a bit more complexity, but I think it's possible. It will be a few weeks before I'm able to work on this.

@cloudy81
Copy link

Hello. Are you working on that issue? Is it still planned to realize?
In our organisation we would prefer to have a global config per project.
Maybe it is also possible to have a default config per process template, it would help, to reduce the configuration work when adding a new project and with inheritance we could control the company style guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants