Usage of "Send custom email" postfunction of scriptrunner in workflow

[Mario]

Hi there,

I'm quite new to Scriptrunner und just getting started. I want to use the "Send custom email" workflow postfunction of scriptrunner. Everything is almost fine but there remain two problems:

I'm using this body template:

<ul>
<li><b>Summary:</b> ${issue.summary} </li> <br>
<li><b>Issuekey:</b> ${issue.key}</li> <br>
<li><b>Priority:</b> ${issue.priority} </li> <br>
<li><b>Reporter:</b> ${issue.reporter} </li> <br>
<li><b>Created Date:</b> ${issue.created} </li> <br>
<li><b>Description:</b> ${issue.description} </li> <br>
<li><dl>
<dt><b>All Comments:</b></dt>
<br> XXX
</dl> </li> <br>
<li><b>Text123</b> <br> longer text sentence[...]
</li>
</ul>

1) The ouput of "priority" does not work. Neither in the preview nor in a real testmail. There always occurs:

Priority: IssueConstantImpl[[GenericEntity:Priority][sequence,4]statusColor,#EF612C[name,Very High][iconurl,/images/icons/priorities/major.svg][description,][id,10200]]

What am I doing wrong here? I just cannot figure out what is causing this?!

2) I need to include all comments of the issue (incl. a comment added during the transition of the triggering post function). Previously I've used the jmwe email issue postfunction, but it was limited as I need to change the real From-Sender-Address --> therefore I switched to the scriptrunner postfunction.

In the jmwe postfunction I used this code successfully (provided by the jmwe community leader) to catch all comments:

<%= issue.get("comment").collect{"<dd><li>"+it.bodyHtml+"</li></dd>"}.join('\n') %>

This does not work anymore in the template mentioned above.

How can I achieve in the scriptrunner postfunction to include all comments (at position XXX) of the affected issue in the template?

Thank you all very much for your help in advance.

Best regards
Mario

[appsmaticnet]

Using "Bulk Edit " on parent task I was able to move sub-task from sprint-1 to a new sprint  then following the wizard choosing "Move Issues"  in "Operation Types" step to move target sub-task into the same project as "Story"

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Bulk Edit -> Move can not change the sprint on an issue (and certainly not a sub-task because they do not have sprints), but you can use it to change the parent issue.  So I suspect what you have done is changed the parent to an issue that is in the current sprint.

[Nic Brough -Adaptavist-]

You do not.

Sub-tasks are not sprint items, they don't go into sprints themselves. 

They can be thought of as being in a sprint only when the issue that they are a part of is in the sprint.

What you are doing is not good practice and it certainly is not Scrum or Agile.  It sounds like you should be raising bugs as sprint items (stories) and putting them in the backlog as usual.

[Garden16]

They can be thought of as being in a sprint only when the issue that they are a part of is in the sprint. 

Here in this scenario, the bug issue type belongs to a certain sprint 

How do I transfer open defect subtasks from Sprint 1 to Sprint 2? It is possible to create an automated rule that moves all defect subtasks that are not closed to the bug issue type for the second sprint.

1: Sprint 1 -> Bug issue type -> 1: Defects subtasks - status - Closed  

                                                   2: Defects subtasks one - Status - Open

2: Sprint 2 -> Bug issue type-> Add  the Open status Defect subtasks from sprint 1 under sprint 2 Bug issue type

I need an  automated flow to transfer the open status defect subtasks to move under the next sprint's bug issue type

[Nic Brough -Adaptavist-]

Again, you do not transfer sub-tasks between sprints.  Sub-tasks are not sprint items, they're only in a sprint because their parent is - they are a part of their parent story.

The parent story is not done if it has open sub-tasks, and when that moves into the next sprint (because it is not done) all the bits of it move with it.

Quite simply, you do not need to automate anything here, Jira handles it all for you, off-the-shelf.