Page History

When to use this workflow post function and when to use an automation rule?

This use case is very useful, if repetitive issues have to be created in only one project or workflow. Then a post function is the easier way to go.

But if this setup is needed for several projects, the Create issue action would make more sense.  In this case you might want to check out our corresponding automation use case.

Add a Create issue post function to the desired workflow transition.

Issues to be created

toStringList(%{issue.cfnnnnn})
# Replace the field code with the one of your custom field. Use the field dropdown to automatically insert the field code.
# You can use any field supporting multiple options, e.g. checkboxes or multi-selects.

Summary

Enter the following expression

%{seed.text}
# This is a reference to each value returned by the text list.

with parsing mode set to Advanced Text

Description

To enrich the issue with further information, you might want to add a short description. It is not mandatory, though.

Run as

User

Choose Current user