How to have sub-tasks inherit Fix Version field from their parent ticket in JIRA Cloud

[Uliana Elliott]

I'm revisiting an old thread from 2017 but with a slightly different take, now specific to Jira Cloud.

I’ve successfully set up an automation rule that makes sub-tasks automatically inherit the Fix Versions field from their parent issue. This works as intended only if the Fix Versions field is visible on sub-tasks and present on the Edit screen.

The issue is: while the automation works, the field remains editable on the sub-task which I would like to avoid.

Is there a way in Jira Cloud to make the Fix Versions field read-only on sub-tasks, while still allowing it to inherit the value from the parent ticket via automation?

Thanks in advance for any insights!

[Izabela França]

Hello @Uliana Elliott ,

I would suggest using operation screens to achieve that.

First, separate the sub-task screens by creating one for each operation (Create, View, and Edit). Then, remove the Fix Versions field from the Edit screen, but keep it on the Create and View screens. As a result, the field will be “read-only” for users, but the automation will still be able to update it.

Let me know if that works for you :)