When I use Script Runners function "Create a sub-tasks" to create sub-tasks during a workflow post condition, it copies the Story Points from the parent to the newly created sub-task as well, which does not make much sense in our opinion.
So, now I'm clearing the field via the Additional issue actions. Why is this field copied from parent?
We have Script Runner version: 3.0.16. Plan to update to the paid version next year.
I would imagine that all fields are being copied by the script. It's not looking at the words "story points" and deciding not to copy it, the logic is much more simple than that. Foremost, I would not recommend using Story Points on Sub-Tasks, so the easy fix here would be to hide that field within the sub-task field configuration for your project.
Secondly, you should take the Create Sub-Task script, which is included within your Script Runner package, the
.jar file you've installed within your JIRA. You can open this file and locate all of the scripts, which are written in Groovy. This script should then be customized to fit your needs. So in this case, you'd desire logic to not copy the Story Points field, but otherwise remain the same. Then, you can use this script instead.
Thanks for your reply. However, I cannot disable story points on sub-tasks as quite a few projects want to use it (although I recommended against it), but still I would prefer having control over the fields being copied. Creating a subtask is not the same as creating a cloned issue. But thanks for your suggestion to customise the groovy script.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG