You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a custom field called 'Request Type' on my Jira Cloud instance whose value doesn't get replicated in the subtasks ( we have a ton of them). As a result, when categorizing by Request Type, over 50% of tickets don't have a Request Type greatly impacting accurate reporting. I've tried setting up an automation rule via the "Edit Issue Fields" action as advised in the community. However, am getting this error.
When I go to the advised "Edit Request Type", I don't get the option to copy the value from the Parent/trigger issue and I have to choose a specific type?? I just need the subtask to assume the same value as the issue that created it (ie. Parent).
Hello @Kay Kalunga Kabwe ! Welcome to the Atlassian Community!
I think the name of your custom field is the same name as the system-defined custom field Request Type and this is confusing your automation. You may be selecting the system field instead of your custom field.
As a test, rename your custom field and see if you can get your automation to work.
That's the system field Request Type. That's why you can't edit or modify it.
Did you create a custom field or are you using the Request Type provided by the system? If you are, it's only meant to associate with a parent type, not a subtask type.
Interesting. Normally the Request Type field isn't on the default subtask screen.
Anyway, here's more information.