Hi community,
how are custom fields bound to projects? There seem to be two ways:
1.
(custom) fields -> Masks
Masks + Issues (like create, edit...) = Screen Schemes
Screen Schemes + ISSUE TYPE = Screen Scheme for Issue Types -> Project
2.
Fields -> Masks
Masks-> Field configuration
Field configuration + ISSUE TYPE -> Field Configuration Scheme -> Project
So there are two different ways of how a custom field is connected with an issue type and later to the same project.
Isn't it possible, that a field is connected on the one way with one issue type and on a second way with another issue type but to the same project?
Wouldn't they interfere with each other?
I'm not sure which way to prefer.
Hi Luca,
Imagine two levels of hierarchy for different use cases. 1-per issue type, 2- per project
When you create a new custom field, it is added to all projects using that issuetype (and the associated screen scheme). However, you can restrict that field per project by adding a context. i.e
screen schemes are meant for associating the field to an issue type across all projects. The second option - field configuration scheme is only relevant if you want to associate a field with a particular project(s) and not with all projects using that issue type.
I would prefer Option 1 but thats just a personal choice.
Hello,
You are right if a field is not configured for a project in the field context, then even if you add this field to a screen in this project, the field will not be visible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Want to make your everyday Community actions directly contribute to reforestation? The Atlassian Community can achieve this goal by liking a post, attending an ACE, sending your peers kudos, and so much more!
Help us plant more trees
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.