Features used to implement the example
Example: Add all assignees of certain sub-task types to a "Multi-User Picker" custom field
I'm trying to copy the assignee from only a specific type of sub-task to a multi-user field on the parent ticket. There could be any number of the specific type of sub-tasks (0-999) as well.
Can this function handle this logic?
I have an additional feature I'm trying to add that is somewhat related as well. For each of a certain type of sub-task, there is a start date field and an end date field. I want to copy the earliest of all the start dates and the latest of all the end dates to a start date field and end date field on the parent ticket.
I explain how to implement first functionality: Let's suppose we have a Multi User Picker custom field called "Team", and we want to select on that field all the assignees of sub-tasks of type "QA Sub-task".
We use post-function Read fields from linked issues or sub-tasks with the following configuration:
We use post-function Copy a parsed text to a field with the following configuration:
Note that:
We use prefix '+' in order to add all users contained in field "Ephemeral string 1". If we used prefix '-' instead, we would remove those users. If we didn't use any prefix, we simply would replace currently selected users in field "Team" by those contained in field "Ephemeral string 1"
%{00061} is field code for virtual field "Ephemeral string 1"
Once configured, transition would look like this:
I explain now how to implement second functionality (third functionality is obvious once explained second one): Let's suppose we want to overwrite Date Picker custom field "Start Date" with the earliest value of that field in all sub-tasks of type "QA Sub-task", or doing nothing in case parent issue contains an earlier value than its sub-tasks do.
We use post-function Read fields from linked issues or sub-tasks with the following configuration:
Once configured, transition will look like this:
Other examples of that functions
Read fields from linked issues or sub-tasks
- Add all assignees of certain sub-task types to a "Multi-User Picker" custom field
- Add and remove a single or a set of items from multi valued fields
- Copy "Due date" into a date type custom field in a linked issue if it's greater than current issue's "Due date"
- Copy attachments from one issue to another
- Make an issue inherit highest priority among those of linked issues
- Propagate highest priority from blocked issues to blocking issues
- Sum sub-task's "Time Spent" (work logs) and add it to a certain linked issue
- Add all assignees of certain sub-task types to a "Multi-User Picker" custom field
- Add and remove a single or a set of items from multi valued fields
- Add current user to comment
- Add or remove request participants
- Add watchers from a part of the issue summary: "Summary_text - watcher1, watcher2, watcher3, ..."
- Assign issue based on the value of a Cascading Select custom field
- Assign issue to last user who executed a certain transition in the workflow
- Automatically close resolved sub-tasks when parent issue is closed
- Automatically reopen parent issue when one of its sub-tasks is reopened
- Calculate the time elapsed between 2 transition executions
- Close parent issue when all sub-tasks are closed
- Combine the values of several Multi-User picker fields
- Compose a parsed text including the "full name" or a user selected in a User Picker custom field
- Compose dynamic text by inserting field values in a text template
- Copy issue labels to a custom field
- Copy the value of a user property into a user picker
- Create a comment in sub-tasks when parent transitions
- Execute transition in epic
- Getting the number of selected values in a custom field of type Multi Select
- Limit the number of hours a user can log per day
- Make a sub-task's status match parent issue's current status on creation
- Make parent issue progress through its workflow
- Moving story to "In Progress" when one of its sub-tasks is moved to "In Progress"
- Moving story to "Ready for QA" once all its sub-tasks are in "Ready for QA" status
- Parse Email adresses to watchers list
- Parsing text from last comment and appending it to issue's summary
- Remove versions selected in a version picker custom field
- Replace certain issue link types with different ones
- Restrict parent issue from closing if it has sub-tasks that were created during a given parent issue status
- Set a Select or Multi-Select field using regular expression to express the values to be assigned
- Set assignee depending on issue type
- Set field depending on time passed since issue creation
- Set priority for issues that have been in a certain status for longer than 24 hours
- Set security level based on groups and project roles the reporter or creator are in
- Transition linked issues in currently active sprint
- Transition only a sub-task among several ones
- Transition parent issue only when certain issue sub-task types are done
- Update Cascading Select custom field with a value of the field in parent issue
- Update checkboxes custom field if a file has been attached during a transition
- Validation on issue attachments
- Validation on MIME types of issue attachments
- Writing a comment to blocked issues when blocking issues are resolved
