behavior of the field

[Samrat.bodapati@gmail.com]

How to use behavior functionality

--- the stuff below is the original question, re-instated in an attempt to make the answer make sense.  We don't know who edited the question to downgrade it ---

I want to have the same configuration shared by all the projects so if a change is needed we can update all the project at once.

This means all projects should use the same:

• Issue type scheme
• workflows per issue type
• workflow schemes
• screens
• screen schemes
• issue type screen schemes
• custom fields
• field configuration
• field configuration scheme
• permission schemes

I need  an overview what needs to be done and what impact it would give (differences between the projects)

[Nic Brough -Adaptavist-]

There are three things that jump out at me:

• In most cases, create the schemes you want, apply them to the projects, and you are done.  The projects will behave the same.
• Custom fields have a quirk in that they have "context" which is not handled by a scheme.  You'll need to check that in the list of custom fields for each of them.  (Although if you set them as "global" you won't have to worry)
• The other differences will depend on how you have configured things for groups/roles and how users are added to projects.  Stick to using JUST roles in your permission schemes (never groups) to keep it simple.