Known issues common to all post-functions:
Filter by label (Content by label) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Troubleshooting this post-function configuration: In case the post-function does not work as expected these are the things to look out for
Filter by label (Content by label) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
When you add this post-function to a transition and trigger the transition, the add-on deletes the target issues.
Run As
Run as current user: The current user will be the user that deletes the new issue.
Run as add-on user: The add-on user will be the user that deletes the new issue.
Run as this user: Any user selected in this field will be the user that deletes the new issue.
Conditional execution
To execute this post-function based on the result of a Nunjucks template see Conditional execution. executionUse case
A typical use of this workflow post-function is to delete an issue. Consider a use where you want to delete an issue and its subtasks once rejected. To configure it:
Add the “Delete issue” post-function to the “Reject” transition of the workflow
Save the post-function
Publish the workflow