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

Create Subtask - 7.x

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 6 Next »

On this page

Description

Using the Create Sub-task workflow post function will allow you to create one or more sub-tasks when the post function is processed after a workflow transition step. We've streamlined the configuration of this post function by grouping all configuration settings into various tabs for easy access:

  • ISSUE FIELDS - These issue fields allow you to define the contents of one or more fields when an sub-task is created by this post function. Substitution Variables can then be used to populate fields. Issue Fields are grouped into the following common categories:
    • Basic Fields - includes fields which are most commonly used when creating a new sub-task in Jira.
    • Detailed Fields - includes details associated with the sub-task, people involved, and dates.
    • Links - includes details of sub-task links and link types.
    • Comments & Attachments - how you want to handle comments and specifics associated with attachments.
    • Custom Fields - controls whether to copy custom fields and allows you to define values for new custom fields.
  • OPTIONAL RULES - Allow you to define the additional criteria for when and how to create the sub-task(s). Optional Rules are grouped into the following category:
    • Conditions & Configuration - Define one or more conditions for when to create the sub-tasks(s), use JQL to define substitution variables to be used to populate other fields, as well as set the acting user for the sub-task creation. 
  • HELP - Provides quick links to additional documentation 

Example

This scenario introduces a new Create Sub-task workflow post function to a transition step within an existing workflow.

Background

Our scenario uses an example ePub workflow that helps teams coordinate the publication of electronic books. While transitioning from the "Open" to "In Draft" steps, let us create a new sub-task within a specific IT Services project in our Jira instance. This creates a sub-task issue in the backlog of our Digital Publication team, so their manager can begin to forecast and assign resources. 

Steps

Configuration Settings




  • No labels