This new feature gives you even greater flexibility when applying issue templates, letting you create only the child issues you need - without requiring the parent issue to be activated.
Imagine this: you’re working on a complex template with a hierarchy of tasks, but not all of them are relevant right now. Previously, deactivating the parent issue meant automatically deactivating all its child issues. With this update, you’re in full control. You can now reactivate specific child issues while keeping the parent issue deactivated. It’s flexibility at its finest!
And don’t worry - if you’re dealing with subtasks, we’ve got you covered. Subtasks still require a parent issue to function in Jira, but you can easily assign one dynamically using Templating.app’s variable options or manually during template application.