Within groovy listener context, I was able to create a subtask fine, based on a condition. Basically, if "Doc Required" field is checked to "yes", create a sub-task. The snippet as follows -
cfValues['Doc Required']?.getValue() == 'yes' && ! issue.subTaskObjects.any {it.issueTypeObject.name == "Bug"}
where "Bug" is the Issue type in parent ticket. This does create sub-task.
Now, I set the Target issue summary as:
issue.summary = '[doc-subtask]' + issue.summary
also set the custom field as issue.assigneeId = 'docs@xyz.com'
The problem is when the sub-task issue is created, it takes only one of the two. Sometimes it takes up issue.summary while some other times, it takes up issue.assigneeId. But not both of them together.
How can I have both of them together, in the sub-task ticket ? Also, see if my approach is right for what I am describing.
Jamie - thanks for your time.
dvps-177-picture.PNG
try:
Additional issue action:
issue.assigneeId = "<UserName>" issue.summary = '[doc-subtask]' + issue.summary
Udo - thanks and it works. sorry for overlooking the fact that the issue action text box can hold multiple lines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join PM Evangelist, Axel Sooriah, & Product Ops. Consultant & Advisor, Jenny Wanger, as they unpack the role of product ops and discuss key takeaways in Atlassian’s ‘The Product Ops Mission’ guide. They’ll answer your questions live on May 6 at 9:00am PT.
Register here ⬇️Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.