Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null
Skip to end of banner
Go to start of banner

How to create subtasks on initial issue create

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Description

The create subtask transition post function can also be used when issues are first created. 

Steps

  1. Edit your workflow - create a draft if necessary

  2. Go to the Open step

  3. Click on the Create Issue (1) incoming transition

  4. Go to Post Functions

  5. Add  Create sub-task on transition post function

  6. To prevent looping, make sure you set the condition to ignore create if the issue is a subtask: 

  7. Set other parameters as you need

  8. Move the post function below the Creates the issue originally post function - This is important!

Looping hazard

Be careful! Your configuration must have looping prevention included. Follow the instructions carefully and make sure you test carefully on a test instance or at least a test project.


What about creating issues?

Looping hazard

Be careful! Your configuration must have looping prevention included. Make sure you test carefully on a test instance or at least a test project.

That can be done using the same techniques, but you must be more careful to set the appropriate conditioning parameters to prevent looping. Use a test instance and double-check your logic as the result of an error is bad (sad). Preventing looping is more difficult with issues compared to subtasks. You will need some specific conditions according to your environment. For instance, a value for a custom field that will indicate to create or not to create an issue. Or perhaps a JQL query that will indicate to not create.

  • No labels