Avoid creation of sub-task with parent info

I noticed all sub-tasks are being created with Parent info (Fix Version/s). In my workflows configuration the Fix version is a mandatory field (bug-workflow), except for sub-tasks (sub-tasks-workflow).

I have checked the options of the create transition on the workflow assigned to Sub-task issue types and there are no options to include parent info, in fact, I have added a Post Function on the Create transition to clean the field of Fix Version/s when the sub-task is created, but it didn't work. 

Do you have any ideas why this is happening?

2 answers

It definitely shouldn't be as it doesn't on mine with all of my built-from-scratch workflows, but not sure as to what yours may have in it that shouldn't be there.  Going to try to look it up before writing an answer

As mentioned in my comment on your question, if you build your workflows from scratch, this should definitely not be happening as you wouldn't have any additional function or property making certain fields be carried over (yes, based on my own program's system, but I'm 99% confident in this assertion).

Even though you said that you have checked your sub-tasks-workflow Create transition for unnecessary functions, please verify through the resolution in this link that you do not have a create transition "Set field from parent" post-function for Fix Version. https://confluence.atlassian.com/jirakb/how-to-automatically-map-fields-of-a-parent-ticket-to-a-new-sub-task-in-jira-cloud-779160741.html

In fact, what are your sub-task-workflow's post functions for Create? My built-from-scratch workflows for example came default only with the following create post-functions:

  • Create the issue originally
  • Re-index an issue to keep indexes in sync with the database
  • Fire a Issue Created event that can be processed by the listeners

For any workflow I have, I believe these are the only 3 post-functions set. 

Thanks Geoff,

The workflow was not created from scratch. 

My current options are:

  • Creates the issue originally.
  • Fire a Issue Created event that can be processed by the listeners.

I added the re-index option and keeps doing the same.

Is there a way to 'debug' a workflow?

 

Don't know about debuging per se.
By any chance, nobody installed plugins like this did they?
https://marketplace.atlassian.com/plugins/com.atlassian.jira.copy-to-subtask-plugin/server/overview

@Geoff Wilson actually I created a workflow from scratch but it keeps doing the same thing. I will try to do something else and let you know.

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
Published yesterday in Jira

Mission-critical battery manufacturer fulfills FAA software requirements with Commit Policy Plugin

EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...

165 views 0 2
Read article

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