create sub tasks from issue on transit
Hi I need to create two sub-tasks: 1. first subtask * Summary = Define Specification for <Feature Name> (parent summary name) * assign to Component owner of "Component Architecture"
- 2nd task * Define Test plan for <Feature Name> (parent summary name) * assign to Component owner of "QA"
Can you assist? Thanks
Comments (7)
-
repo owner -
reporter I get the following error
Configuration
Postfunction
-
reporter Can we do a separate issue creation?
create 1 Sub-Task where Summary = "Define Specification for <Feature Name>" (parent summary name) and assignee is the Component Lead of "Component Architecture"
Create 1 Test Plan issuetype linked with "Requirement Relates to" issue link to the current issue, where summary = "Define Test plan for <Feature Name>" (parent summary name) and assignee is the Component Lead of "QA"
Sorry for the hassle and Thanks
-
repo owner Yes, you can use 2 separate post-functions, but please, try the following string list expression for the assignee:
getMatchingValue(^% = "specification" ? "Component Architecture" : "QA", availableItems(%{00094}), availableItems(%{00125}))
-
reporter The problem is that actually i need 1 sub-task, and 1 linked issue, and to my understanding it is one or the other per post function Correct?
-
repo owner Each post-function can create only one issue type, so you need 2 different post-functions.
Each post-function will create only one issue, so you don't need to use seed strings, You can compose the summary using basic parsing mode, and inserting field code %{00000} for the parent's summary.
For the assignee you should use the following string expressions:
getMatchingValue("Component Architecture", availableItems(%{00094}), availableItems(%{00125}))
and
getMatchingValue("QA", availableItems(%{00094}), availableItems(%{00125}))
-
repo owner - changed status to resolved
I close the issue. Please, reopen it if you need further support on it.
- Log in to comment
Hi Itamar,
Use "Create issues and subtasks" with a configuration similar to this one:
1) Seed string expression is:
2) Summary string expression is:
where %{00000} is field code for summary.
3) Assignee string expression is:
where %{00094} is field code for Components, and %{00125} is field code for Component leaders.
I'm assuming that "Component Architecture" and "QA" are the exact names of the 2 components.
Once configured, the post-function looks like this: