Create sub-task type reverting

[Nathan Ostrander]

I am trying to create sub tasks using automation in one of my spaces. When I set the work type, click out of the object and click back in the work type defaults back to the first sub task type in the list. I also tried hitting next to see if that would save the type, but that did not work either.

[Trudy Claspill]

Hello @Nathan Ostrander 

I don't seem to be able to recreate your experience. Can you tell me if I am doing something different from you?

1. Add the Create Sub-task action.

2. Pull down the Type field.

3. Select the not-first sub-task type. Type field is filled with selection. Click the Summary field.

4. Type in a summary. 

5. Click Next

6. Click on the Create Sub-task step. See that Type is still set correctly.

I've tried the same steps with multiple sub-tasks in the one action.

I'm using Chrome in an Incognito window.

Have you tried a private browser window, clearing your browser cache, or a different browser application?

[Nathan Ostrander]

I was able to recreate the issue in incognito in both Edge and Chrome with a cache clear as well, but it seems to be just a display issue. If I go back through and set all of the sub-tasks to the correct work type and update the automation it does create the correct type when the automation is triggered even thought when I click the automation again they will default back to Work Order. 

[John Funk]

Hey Nathan,

I would suggest creating each Sub-task as a separate Create work item action in the rule instead of doing multiple ones in a single step. 

[Nathan Ostrander]

I agree, John, that this would likely fix the problem, but this seems like a bug to me that should get fixed. When we are limited to 65 components in an automation, being efficient and using Create sub-tasks has a lot of benefit. 

[John Funk]

Are you sure that each one of the Sub-tasks don't count as a component? Because if you put multiple Conditions in the single Trigger step - each of those is counted as an action. 

But yes, you should report it to Atlassian as a potential bug. 

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

But you also might want to test with different browsers or Incognito/Private window mode first.