Default value of custom field is set to every sub task

[Michael Steinmüller]

Hello @AlL,

we're using Jira Service Desk (hosting type Server) with the addon "Automation for Jira".

We want to use this addon for our employee onboarding process.
If the user select "new notebook" or "windows account needed" in the customer portal form, the automation creates a sub task "Prepare a new notebook" or "set up a new windows account".

In the custom field "Default Accounts and Systems" (type: check box)  we've set "Windows Account", "IBM Notes" and another option as default, so in the customer portal the default values are set automatically.

The problem is, that as soon as I set the default values for this custom field, Jira sets this custom field to every other sub task on the ticket (e.g. "Create SAP Account", "Prepare smartphone"...). Even if I don't select this custom field in the sub task creation over the automation addin.

Is it possible to set the default values without having this custom field in every single sub task?

Thanks a lot.

Kind regards,

Michael

[Michael Steinmüller]

Hello Mark,

here are the screenshots. I've changed the language to english for you:

The fields I want to get in the subtasks are marked:

In the created subtask it should look like:

For this subtask there is only the software "IBM Notes" needed for the account creation.

But in other subtasks the custom field "Benötigte Zugänge/Systeme (allgemein) is NOT configured in the project automation.

But it still shows up in the other subtasks, with the default values (Windowsbenutzer, IBM Notes, D3):

Hope this helps you out.

Kind regards

Michael

[Mark Segall]

Thank you @Michael Steinmüller I think I understand now.

You'll want to leverage an If/Else condition.  Here's a quick sample where I create issue logic based upon different priorities:

[Mark Segall]

Hi @Michael Steinmüller and welcome to the community

I would need more information on the project itself, but if this is a Company-Managed project, you can add a new context on that custom field with no default set and assign the context to the Subtask issue type.

[Michael Steinmüller]

Hello Mark,

yes, the project is a company-managed project. I have full access to the administration interface.

All of the used subtasks are the same subtask issue type "subtask employee onboarding".

If no default value is set, the custom field only appears in the subtasks where the custom field is set (over the subtask creation mask in the automation plugin).

Thanks in advance.

Michael

[Mark Segall]

Hi @Michael Steinmüller - Can you share a screenshot of your automation rule?