Child work item table and List view does not respect edit screen – still possible to edit inline

[NC M]

Hi,

I work in two different instances of Jira. For stories, we do not want to use the system fields Original estimate and Story points. So I want these disabled and locked for editing, so no one can set any value in these.

For both instances of Jira, Original estimate and Story points have been removed from the edit screen for stories.

• For instance 1: It is possible to edit both fields using the child work item table in epics and the List view.
• For instance 2: It is only possible to edit Story points from the child work item table in epics. Not Original estimate. I believe I have looked through all settings, and everything appears the same for both instances. Both fields are, however, able to be edited using the List view.

Quesitons:

1. What am I missing? How can it be possible to edit both, when they are removed from the edit screen, and how can their be a difference in the two instances?
2. Is it possible to disable the fields from anyone for stories, so they cannot even be searched when selecting a column in child work item table or List view? Seems strange, that you can find fields, that have been removed from the screens.

Documentation:

• Customize the child work item table - indicates the edit screen controls what can be edited from the child work item table.
• https://jira.atlassian.com/browse/JRACLOUD-95659 - this indicates, that there's a bug with the List view, but mentions nothing about the child work item table.

[Christos Markoulatos -Relational-]

Hi @NC M welcome

The difference between your two instances is most likely down to field configuration rather than screen configuration. Original estimate is part of Jira's time tracking system field, while Story Points is a separate custom field, and they can behave differently depending on how time tracking is configured at the project level. It's worth checking whether time tracking is enabled or disabled differently across your two instances under project settings, as that can affect whether Original estimate surfaces as editable in views that bypass screen schemes. 

On your second question, there is currently no native way to prevent a field from appearing as a selectable column in the List view or the child work item table. The column selector in the List view surfaces any field that is associated with at least one work type in the space, regardless of whether it is on any screen. You can hide a field from the work item detail view using the Hidden fields section in the issue layout, but that does not carry over to the column picker in those views.

Hope this helps!

[NC M]

1. Time tracking should be enabled same way for both instances.
2. How would I prevent someone from setting a specific field then? Set an automation to be, that whenever a value is entered in that field, it should be set to 0? And is it correct for a number field, I can only set it back to 0 and not NULL? There is a different in the system between how these two are handled. Any way to set it to NULL after a developer has entered something in the field?