with the easier options available from user interface the labels are likely replaced and overwritten. You need to add them using advanced field edit (using JSON).
There was a previous post which seems to discuss this a bit more elaborate, from what I remember for sub-tasks it was reported to be possible but not so easy:
Please note that the scenario was not 1:1 identical.
The core part to probably look for is:
In that case the user wanted to copy to sub-tasks - but you would need the other way around. So you need to make sure you adapt parts of the logic, for example like Fabian said to pay attention for the proper branching.
Take a look at this video tutorial: https://www.google.com/url?sa=t&source=web&rct=j&url=https://community.atlassian.com/t5/Automation-discussions/Jira-Automation-Video-Tutorial-on-how-to-keep-Parent-and/td-p/1783535&ved=2ahUKEwinnb-g5eLyAhVKbs0KHXiNBqAQFnoECCcQAQ&usg=AOvVaw1bmoebALLxkaFZHol4F6v0
Youbare looking at rule #2, instead of branching to the subtasks you will branch to the parent instead.
Welcome to the community!!
Automation rules can be used to achieve this. The rule can be triggered when the label on a sub-task is updated and the value can be copied to the label for the parent.
Please let me know if you have further queries on this.
Kindly accept the response if this helps in resolving the query.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events