Transition parent issue to another status

Basic configuration*

Choose Parent issue.

Choose transition to status.

Choose Open as the status to be transitioned to.

After checking if the parameters match this example, you can click on add and this is how the post function should look like.

Now that you are familiar with this post function and what it does, you can configure the parameters based on your needs.

Use case	Type	Function	Use case description	Complexity
Add a hyperlink to an issue in an email
Add assignee as watcher to every blocking issue
Add a table with the elements of a text to an email
Add attachments from current issue to cloning issues
Add comment with the request participants' display name
Add days skipping weekends and holidays to a Date Picker field
Add or remove request participants
Add percentaged profit margin when closing issue
Add user to field depending on selected options
Add watchers ignoring inactive users
A developer must not execute the transition
All blocking issues must be resolved
Assignee may only have a restricted number of assigned issues
Assign issue to the default user of a role
Automatically create a version when starting the release
Automatically link an issue to an external one
Automatically log work on a Jira issue
Automatically log work spent in a specific status
Block an Epic's transition until all the issues under that Epic are resolved
Calculate custom sequence numbers
Change the assignee to the next evaluator
Clone epic, tasks and sub-tasks
Clone issue in external instance
Copy excerpted value from new comments
Copy formatted description of issue into email
Create a comment on an external Jira ticket
Create a component to group issues related to UI design
Create a new employee account during an onboarding process
Create an external project for a new employee during an onboarding process
Create an issue with a custom summary

If you still have questions regarding this example or others, feel free to refer to our support team.