This question is in reference to Atlassian Documentation: Configuring sub-tasks
Hello we are using JIRA 6.3.7 with according JIRA Agile Plugin installation. I recognized that when creating a subtask of an issue the component field is inherited from parent, which is undesired behaviour. I guess this is implemented in JIRA Agile, when switching plugin off everything works as expected, while switched on the component field appears with same components as parent issue. How to remove this behaviour? Is there any setting to do so? Or do I really need to write a script to remove components in case it was left blank on creation?
Okay, agreed! The JIRA agile is copying the basic system fields (such as Component(s), Priority, FixVersions,etc..) from it's parent task automatically. Its mentioned here: https://answers.atlassian.com/questions/260020
Luckily, I believe the fact is that, JIRA is copying these fields only if it is left empty. Please confirm this.
If it is true, we can add a post function to clear these fields if not required.
this is true... but I want this field to be optionally be filled by the user. So it can be left empty at the beginning and the function group, processing this subtasks, will enter affected components, which are collected at main issue... I don't need components be inherited, since it will confuse the users.
I used groovy script executed in subtask postfunction of create transition:
this checks if the components are empty, if yes it explicitly sets component field to be empty
in any other case I don't touch component field, so it will take already entered components on create screen
this does the trick
I first checked for components equal to parent, but that doesn't work out
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot