Associate 2 screen schemes for one issue type in one project
Asked by Yuliia Vyborova:

Hi! I want to freeze some fields in my custom issue type called Feature Project. I use PBM Projects Issue screen scheme but I want to add Frozen PBMP Screen Scheme to the same project called PBM Projects. Is it possible? If not, can you please advice how can I lock from editing some fields (Release version and 2 custom fields)? Much appreciated!

![Screenshot 2024-09-16 at 4.45.53?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347545i9E21951CCD09A46D/image-size/large?v=v2&px=999 "Screenshot 2024-09-16 at 4.45.53?PM.png")


Answers:
author: Walter Buggenhout
body: Hi [@Yuliia Vyborova](/t5/user/viewprofilepage/user-id/3597151),

No. A project can only have one issue type screen scheme. This, in turn can contain multiple screen schemes - one screen scheme per issue type in your project.

*(At risk of creating confusion, a screen scheme can finally contain 3 different screens: one to create, one to view and one to edit issues)*

If you want to restrict the editing of certain fields, you should be able to do so by removing those fields from the *edit* screen associated with the issue type you are referring to.

In your project settings, if you navigate to *Issues \> Screens* and expand the screens listed under your issue type, you should be able to see which screens are being used to create / view / edit issues of that specific type.

It often happens that the same screen is used to edit and view an the same issue type. If that is the case, you should add an additional screen (the easiest way is to copy the current screen), remove the fields you don't want your users to edit and add it to the screen scheme for the specific issue type.

One last caveat: it's worth checking if your issue type screen scheme and associated screen schemes are used across multiple projects. If that is the case, be aware that updating existing screen schemes will affect all projects where they are used.

Hope this helps!

comments: author: Yuliia Vyborova
body: Hi [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) . Thanks for the detailed instructions - that helped! Now I see that those fields are not editable. Although, that's probably an interim method. Our end goal is to keep track of changed Release version. That's said, once Release version is set and someone wants to edit it, we never can find what project was updated (notification with field update are not helpful cause you need to manually open each email and compare if the Release version changed). The easiest way is to send notifications once Release version field is updated to some channel. But this also doesn't help once you want to get some report of features planned for a specific release vs current state (what features slipped?). Do you have some advice on how effectively track this? Appreciate any consultancy on this


author: Yuliia Vyborova
body: [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) I got an issue. I set another screen scheme with excluded fields (called Non-editable PBM feature project screen). This screen is used for 2 issue types Infrastructure project and Feature project. Release version field is visible and not editable on the Infrastructure project but not visible on Feature project, although it uses the same screen scheme. Why field is not visible on Feature project? this issue has major impact on other automations that use Release version so I need to resolved this ASAP. Do you know why that is the case?


author: Yuliia Vyborova
body: ![Screenshot 2024-09-17 at 8.47.11?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347814iA99F2BEFC2BCA6E7/image-size/large?v=v2&px=999 "Screenshot 2024-09-17 at 8.47.11?PM.png")![Screenshot 2024-09-17 at 8.53.08?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/347817i5791C0B543006AD4/image-size/large?v=v2&px=999 "Screenshot 2024-09-17 at 8.53.08?PM.png")


Tags: cloud

jira-cloud