Automation issue: Move Task type to Subtask

[Pedro Vera]

Hello everyone,

I am working with an automation that moves a TASK to a SUBTASK. In fact, until yesterday it was working correctly (No changes have been made to the project configuration or automation) but today I found that it is giving me the following errors: (The selected issue type is not valid. (issuetype))

I use the "Edit fields" action for the issue type, but I also use the advanced options to determine the "parent" issue. Here is a screenshot of the configuration:

It is a test, in my real automation I use a custom field to determine the parent issue.

I don't know what could have happened because this automation has been working for me for a long time and from one day to the next it has stopped working.

If I do the task manually from the "move" menu I can do it without problems, but the automation does not manage to do it.

To add more information, I am using the same Workflow for Tasks and Subtasks. This part shouldn't be a problem. Also, I am working on a "Next-gen" project.

Thank you very much for the help!

[John Funk]

Hi Pedro,

Not sure that I can be much help, but I can ask some questions. 

If the two issue types are using the same workflow, then you don't need to do a Move to change the issue types. You can just change the value of the field directly. That's what Automation is trying to do. 

So, can you test that for us to see if you can simple edit the field on the screen directly without doing a Move? 

[Pedro Vera]

Thank you very much for replying John,

It is necessary to make a "move", because I need:

- Change the type of incidence from TASK to SUBTASK
- Indicate the "father" TASK of the new SUBTASK (I do this with a custom field, I have made a simpler automation to not complicate the matter and isolate the problem).

If I don't indicate the "parent" TASK, I get this error:

(The issue type is a sub-task, but the key or id of the parent issue was not specified. (issuetype))

Do you know of a different way to do this from an automation?

[John Funk]

I would see if you could Clone it as a Sub-task, but I don't know if it will let you include the parent key at that point. Is the parent always hardcoded like that? 

[Pedro Vera]

Clone it as a subtask is also not an option, because it will be a very frequent action and would create a lot of duplicate issues (tasks).

The parent isn't hardcoded in the main automation, it is taken from a custom field, like this:

The main problem is that everything I mentioned worked before and has stopped working TODAY. Could it be affecting something unrelated to my configuration by atlassian?

Thank you for your answers.

[John Funk]

It could definitely be something with Atlassian. I would open a support ticket for them to investigate. 

https://support.atlassian.com/contact/#/

Good Luck!

Please post back here with the resolution. 

[Pedro Vera]

Thank you very much John,

I'll keep you informed.