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

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!!

2 answers

1 accepted

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.*

0 vote

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.

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

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

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...

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

Mahesh S Community Champion Jun 12, 2016

Yes! This feature comes via JIRA Agile plugin. 

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

91 views 0 1
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you