Prevent JIRA System fields from being copied to SubTasks from it's Parent tasks

[Mariselvam Lakshmanasamy]

When creating sub tasks, it just copying the basic system fields (such as Component(s), Priority, FixVersions,etc..) from it's parent task automatically.

But it should NOT copy certain fields(say FixVersions). The FixVersions field should only be updated on the subtask when it is resolved. How can this be achieved? Do anyone have ideas???

I'm running version 5.0.7

Thanks in Advance!!

[Mariselvam Lakshmanasamy · Accepted solution]

It looks by default JIRA version 5.0.7 inherits basic system fields to sub-task from it's parent task bypassing all the restrictions/functions we put on workflow.

For example, if we add a function on workflow(at the point of creating the sub-task transition) to clear the FixVersions field, JIRA system bypasses this workflow function when creating sub-tasks.

It looks Atlassian has fixed this problem on their release 6.*

[Jobin Kuruvilla [Adaptavist]]

You must have a script or customization that copies these fields because JIRA doesn't do that by default. Find that customization and see if you can exclude the fixVersion field.

[Nic Brough -Adaptavist-]

Actually, yes, it does. I just tried it in 6.1. If the user leaves either version field or the components unfilled, it inherits the values from the parent

[Jobin Kuruvilla [Adaptavist]]

I don't see it in 6.1.1. Tried creating a subtask on a Task which had fixVersion filled in.

[Nic Brough -Adaptavist-]

Hmm. The Jira I tried it with is pretty much empty. One project, 6 issues, two custom fields and using the default workflow.

Maybe it's the Agile or Service Desk plugins doing this...

[Jobin Kuruvilla [Adaptavist]]

I see. I don't have Service Desk but has JIRA Agile. Is that the one? ;)

[Mahesh S]

Yes! This feature comes via JIRA Agile plugin.