Locking fields on an issue page while in Edit mode

jim_0h6oys

Hi,

     We have defined an issue page that consists of multiple tabs.  The data on these tabs corresponds with the state the issue is in.  As the state changes, some fields on the associated tab need to be populated (done during the transition) and others on the tab are populated while the issue is in that state.  We want to prevent the user from going into Edit mode and manipulating fields on tabs that are associated with states that have not been reached yet.

     Is there a way to make fields read-only until a specific state is set for the issue?

 

Thanks,

 

Jim

Earl McCutcheon

Hello @jim ,

In Jira natively, if a field is present on a screen it can be edited on that screen, with some conditional options possible on transition screens, that can be used to restrict a transition directly.

The option to have field level conditions is tied into field level security permissions, and there is a large discussion on this in the following Feature request noting the final decision on adding this functionality is that this is not something that will become a native function in Jira:

• https://jira.atlassian.com/browse/JRASERVER-1330

The best approach is covered in the workaround section of the Feature request, and covered in more detail in the linked KB "How can I control the editing of issue fields via workflow?" .  The approach is to not have the field present on the edit screen, but rather have any conditional fields only present on a transition and use conditions and validators as covered int he "Advance Workflow Configuration"  documentation, 

But Ultimately on the Edit screen directly this is not possible to do this without a third party add-ons that extend the options to restrict fields directly on various permissions sets like "Field Security Plugin for Jira"  or "Secure Fields - Data Security & Privacy" 

Regards,
Earl