I'm not sure if this is the correct StackExchange site for this, so I apologize if it's not.
Is it possible to create subprojects in Redmine and have it automatically inherit the member permissions from the parent project? If I've got User A as Manager and User B as Developer on the parent, I'd like it to automagically set that up on the new subproject.
I've searched high and low and can't find a way - internal or plugin - to do this.
Thanks!
That's actually very simple: All you have to do is to go into the administration panel, display the list of projects, find the parent project and use the copy button to create the sub-project. On the next page you can configure your project, pre-filled with the values of your parent project, and have some more options like copying members.
Of course this works only on creation - once you created the sub-project and you change one project, you'll need to change the other one as well. Fortunately, working with groups makes it very easy (configure access for groups, not users).
This is possible now since Redmine 2.3.0 (see issue #5605 for discussion). When creating (or updating) a project, you can simply check the Inherit members checkbox.
(This option wasn't available in Redmine when this question was asked and answered initially, so I'd be happy if you considered changing the accepted answer to this one, thanks!)
That's not possible. One of the most fundamental facts of the Redmine permission system is that users are members of distinguished projects having one or more roles. The permissions can't be inherited. In fact, the possibility to have an issue tree was added rather late and hasn't yet been reflected in the permission system.
That said, even if it could be done, permissions could only be added, as you can't take away permissions using roles (permissions from multiple roles are always added). So you would end up with only the possibility to add more permissions in subprojects, but not with less.
Related
I would like to use the default django permissions in my project. Base is that there are 3 types of users, a super user and two other distinct type of users. I'm working towards a system with groups and permissions. So add the two different types of users to their groups on creation.
The whole project is TDD (pure for learning TDD) and that means I want to test the permission system all over the project. But testing in Django happens with creating a new db on every test run.
Thats where my problem is. I would like on creation of the db (maybe better on launching server) to create my groups and set permissions on the groups. I'm thinking about south, but that means adding al lot of migration files on every push to the 'master' branch.
Is there a way to run a command on 'runserver' (or something similar) that checks if there are groups, and update/create the permissions on those groups?
You can provide initial data in a fixtures directory (fixtures/initial_data.json) and they will be loaded in your test created db.
Initial data doc
I have a question about working with CustomForms. I would like to implement a function/search in SuiteScript that would search for CustomForm by Name instead of ID. Any suggestions?
Not sure I 100% get the problem, but see if this doen't help:
Remove code from email to support case script that sets field "customForm".
Create specific role for user used to create the cases - don't assign a generic role, like "administrator".
In code for script, specify the role you created in #2 for the login/authentication.
Now, you can flip back and forth between forms from the NetSuite UI by making the needed form the default for the role you created in #2.
All other users will be unaffected, and you won't have to modify the script going forward, except if you have new functionality to add to it.
The other option is to always make the script use the standard case form. That way, you'll never really need to change it. The standard form will contain all custom fields and all standard fields. The only thing you would then need to control is the preferred form by role.
You need to do the development in sandbox environment and test it there completely before doing the production deployment. You can ask your support team to stop for few minutes while doing the deployment and then do a quick smoke test if possible.
Does anyone know of any way to export user and role permissions, and then re-import them on another copy of Sitecore?
I've had a search around, and bar writing a bit of code to do this, doesn't appear to be anything immediately available ...
The permissions are actually stored on the items themselves, not the Role or User objects. There are two ways to export the object like Stephen mentioned, perform the export/import on the item you granted/revoked access to, not the role or user.
There are two ways to do this .. you can make a Sitecore package and add them to that, the other way is to use Serialization which will write text files to disk that you can then restore into another sitecore instance.
The choice very much depends on how many users / roles you have to move. If its just a few, you can use a Sitecore package but if you have a lot you will probably want to use serialization to do it.
More info about each topic can be found here..
Serialization Guide
Info on Packages
We have a need to programmatically access the layouts/ templates of one sitecore site and move it to another site under different folders basically the intent is to restructure the existing site which is already in production.
Could anyone tell me how do we go about it?
Instead of writing a custom "one-time-use" tool for this, I would recommend you to get advantage of a standard "Transfer Items" application. You can find it in Sitecore Control Panel: go to Database > Transfer Items to Another Database.
So, what you basically need to do:
plug in the master database from the target new site to this older site, like "master_new" or something. This will require the web.config modification. The section on SDN about publishing targets should have a guideline how to do this
run the "Transfer Items" application, select the templates / layouts you needs on the first page, select this "master_new" database as a target database and the place in the content tree to transfer to on the second one
run the actual transfer
If your layouts / templates are groups into folders, this process will take the minimal time - much less comparing to creating your custom script...
UPDATE: Some sample code how to trigger this application programmatically:
UrlString url = new UrlString(UIUtil.GetUri("control:TransferToDatabase"));
Context.ClientPage.ClientResponse.ShowModalDialog(url.ToString());
I would look into using Sitecore Powershell Extensions (look at marketplace). It is a perfect fit for a usecase like this.
I am about to start a django project, where I need a base deployment, lets say just for admins initially. Later admins can add instances of my main public site.
Now, one instance will, obviously be separated by dynamic sub-domains. I need to capture sub-domains from requests, and compute accordingly. It has its own base templates, static files, etc (easiest part). It would have set of feature apps (common for all instances, but not the data in their models). And I am thinking of using Django1.2's multiple database support, and try to get one db per instance (* adding dynamically :( , if that is feasible, It will include dynamic db/model creations*). Or I can go for adding an instance foreign_key in all feature apps models, to separate them instant-wise.
If my instances were known prior to deployment, I would have used multiple database support easily by capturing the sub-domains and diverting my ORM calls to concerned db. But, that is not the case. Those has to be dynamic (added as need arises).
Now before I give it a try, to get solution/rid of delusions about it, I would want experts of SO to think about it. I would appreciate the suggestions, insights and of-course criticism.
I can make it community wiki, if suggested. Thanks guys.
Shouldn't you just run a separate Django instance in a each their Apache VirtuaHost? Then, you can have a Django settings file for each instance and they can each point at their proper database. This also simplifies your code because you don't need to map subdomain names to databases inside your views. As a real bonus, your code gets re-usable because it doesn't depend on your complex setup.
Ususally you can do instances of your app with the sites framework.