I have a set of projects today which differ in only a few respects:
Using a "Shared Configuration" sounds scary because I am warned that nothing can differ (e.g., custom field values) without changing the other project. I don't want any scrum or other "trapped" configuration. I just want to be able to "copy" another project and then I can go and tweak as necessary.
Am I asking too much?
Hey Bill,
"Shared configuration" is not all that scary :)
It basically means, your new project will have the same
Issue Type Scheme (issue types available for creation)
Workflow Scheme (workflows associated with the issue types)
Screen Scheme (screens displayed when creating/editing/viewing issues)
Custom Field Scheme (custom fields available to the other projects)
Issue Type Security Scheme
Permission Scheme (permissions associated with the groups/project roles)
Notification Scheme (email notifications sent for the issue actions)
If you would like to customize any of the above configurations to your new project, you can create the project with a shared configuration, then associate the project to a different configuration of your choice.
This is particularly helpful in scenarios where your custom field values may vary. For example, select list options available for Project ABC may differ from the select list options for Project XYZ. In this case, you may want to create a new custom field context for the new project with the different values, create a new field configuration scheme, and associate the new project with it.
Hope that helps.
Regards
Bhushan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.