Use Cases for Post-Functions (Legacy)

• Create a Product Owner project role, with the product owner as the only member.

• Add the Assign to role member post-function to the Create transition of the Bug workflow.

• Select Product Owner as the project role.

• Select the Conditional execution check box Run this post-function only if a condition is verified.

• Input the following code template in Condition.

  {{ issue.fields.issuetype.name == "Bug" }}

• Create a QA project role, with the testers as its members.

• Add the Assign to role member post-function to the transition that leads to Ready for testing.

• Select QA as the project role to look for.

• Add the Assign to role member post-function to the Create transition of the issue workflow.

• Select Support-UTC as the project role.

• Select the Conditional execution check box Run this post-function only if a condition is verified.

• Input the following code in Condition.

  {{ issue.fields.reporter | userProperty("TimeZone") == "UTC" }}

• Add the Assign to role member post-function to the Approve transition of the issue workflow.

• Select the “Target Issue(s)” as “Sub-tasks of the current issue”

• Select Developers as the project role.

• Create a Developer project role, with the developers as its members.

• Add the Assign to last role member post-function to the Reopen transition.

• Select Developer as the project role to look for.
  
  

• Create a Product Owner project role, with the product owners as its members.

• Add the Assign to last role member post-function to the Validate transition of the User Story workflow.

• Select Product Owner as the project role to look for.

• Select Include Reporter option in case a product owner created the issue but was never assigned to it afterward
  
  

• Add the Assign to last role member post-function to the Done transition of the Bug workflow

• Select “Target issue(s)” as “Issues linked to the current issue through the following link type”

• Select “blocks”

• Select Testersas the project role to look for.

• Select the “Conditional execution” option

• Input the following script:

  {% set linkedIssues = targetIssue | linkedIssues("blocks",["status"]) | filter(["key",issue.key],true) %} {{linkedIssues | filter(["fields.status.name","Done"],true) | length == 0 }}

1. Add the “Build-your-own (scripted)” post-function to the transition

2. Input the following Nunjucks template

   {{ "/rest/api/2/issue/:issue/worklog" | callJira(verb=("post"), params={"issue":issue.key}, body={ "timeSpent": "1w" } ) | dump(2) }}

    

3. Save the post-function and publish the workflow

• Add the Clear field value post-function to the Reopen transition of the workflow.

• Select the field Fix Version/s to from Field.

• Add the Clear field value post-function to the Abort transition of the workflow.

• Select the “Target Issue(s)” as “Issues linked to the current issue through any link type”

• Select all the fields to be emptied from Field

• Add the Clear field value of linked issues post-function to the Abort transition of the workflow.

• Select all the fields to be emptied from Field

• Add the Comment issue(s) post-function to the Start Progress transition of the issue's workflow.

• Write the following content in the Comment section.

  {{issue.fields.assignee.name}} has started working on your support request. We will get back to you within 24 hours.

• Add the Comment issue(s) post-function to the Resolve transition of the issue's workflow.

• Write the following content in the Comment section.

  {% set worklogs = issue.fields.worklog.worklogs %} {% set count = 1%} {% for worklog in worklogs %} Worklog {{count}}: Started : {{ worklog.started }} Time Spent : {{ worklog.timeSpent }} Work Description : {{ worklog.comment }} {% set count = count + 1 %} {% else %} No work logged for this issue {% endfor %}

• Add the Comment issue(s) post-function to the transition that resolves the current issue.

• Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”

• Select the issue link type blocks under “Issue Link”

• Write the following content in the Comment section.

  The impediment {{targetIssue.key}} - "{{targetIssue.fields.summary}}" has been resolved.

• Add the Comment issue(s) post-function to all the transitions of the internal issue workflow.

• Select the “Target issue(s)” as “Sub-tasks of the current issue”

• Write the following content in the Comment section.

  {{ issue.fields.comment.comments | last | field("body") }}

• Add the Comment issue(s) post-function to all the transitions of the internal issue workflow.

• Select the “Target issue(s)” as “Sub-tasks of the current issue”

• Write the following content in the Comment section.

  {% if issue.fields.comment.comments and now | date("clone") - issue.fields.comment.comments | last | field("created") | date("clone") < 6000 %} {{ issue.fields.comment.comments | last | field("body") }} {% endif %}

• Add the Comment issue(s) post-function to the Resolved transition of the Story workflow.

• Select the “Target issue(s)” as “Epic of the current issue”

• Write the following content in the Comment section.

  The user story {{issue.key}} - "{{issue.fields.summary}}" has been resolved.

• Add the Comment issue(s) post-function to the Resolved transition of the Bug workflow.

• Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”

• Select the issue link type blocks under “Issue Link”

• Write the following content in the Comment section.

  {{issue.key}} has been resolved. You should get back to the customer.

• Check the Restrict to internal (Jira Service Desk only) option to make sure the customer doesn't see the comment.
  
  

• Add the Comment linked issues post-function to the transition that resolves the current issue.

• Choose the issue link type blocks

• Write the following content in the Comment section.

  The impediment {{issue.key}} - "{{issue.fields.summary}}" has been resolved.

• Add the Comment linked issues post-function to all the transitions of the internal issue workflow.

• Choose the issue link type is Parent of

• Write the following content in the Comment section.

  {{ issue.fields.comment.comments | last | field("body") }}

• Add the Comment linked issues post-function to all the transitions of the internal issue workflow.

• Choose the issue link type is Parent of

• Write the following content in the Comment section.

  {% if issue.fields.comment.comments and now | date("clone") - issue.fields.comment.comments | last | field("created") | date("clone") < 6000 %} {{ issue.fields.comment.comments | last | field("body") }} {% endif %}

• Add the Comment linked issues post-function to the Resolved transition of the Story workflow.

• Choose the issue link type belongs to Epic 

• Write the following content in the Comment section.

  The user story {{issue.key}} - "{{issue.fields.summary}}" has been resolved.

• Add the Comment linked issues post-function to the Resolved transition of the Bug workflow.

• Choose the issue link type blocks

• Write the following content in the Comment section.

  {{issue.key}} has been resolved. You should get back to the customer.

• Check the Restrict to internal (Jira Service Desk only) option to make sure the customer doesn't see the comment.
  
  

• Add the Copy comments to related issues post-function to the transition.

• Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”

• Select the issue link type under “Issue Link”

• Choose The comment added on the transition screen, if any under Comments to copy

• Click on Add

• Create a global transition “Sync Comments”

  • Add the Copy comments to related issues post-function to the transition

  • Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”

  • Select “causes” under “Issue Link”

  • Choose All comments

  • Add another Copy comments to related issues post-function to the transition

  • Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”

  • Select “is caused by” under “Issue Link”

  • Choose All comments

  • Add a few seconds delay

• Click on Add

Now when you trigger the transition on the issue(s), the newly added comments on the issue are added to the linked issue

• Add the Create issue post-function to the transition on whose trigger you want to create a documentation ticket

• Select Documentation from the Project field.

• Select Document from the Issue type field.

• Select caused by in the Link to new issue section.

• Add an appropriate Summary (such as Release documentation)

• Select the conditional execution and write the following template

  {{ issue.fields["Documentation ticket"] | find({"value":"Needed"}) != null }}

• Add the Create issue post-function to the transition Approve of the Story workflow to create a QA ticket.

• Select Same as current issue from the Project field.

• Select Subtask from the Issue type field.

• Select Current issue from the Parent issue field.

• Add an appropriate Summary (such as Validation)

• Repeat the above steps for the Development ticket.
  
  

• Add the Create issue post-function to the Create transition of the Service desk project workflow.

• Select the Development project from the Project field.

• Select Bug from the Issue type field.

• Set Summary field to {{issue.fields.summary}}

• Select caused by in the Link to new issue section.
  
  

• Add the Create issue post-function to the transition Create of the New Employee ticket workflow.

• Select Same as current issue from the Project field.

• Select Sub-task from the Issue type field.

• Select Current issue from the Parent issue field.

• Edit the Summary field value to : Configuring a new computer system

• Repeat the above steps for the remaining tickets.

• Add the Create issue post-function to the Reopen transition of the sub-task workflow.

• Select the project from Project

• Select the Bug in Issue type

• Select is caused by in Link to new issue

• Select the Epic Link field in Set fields of new issue.

• Write the following in the Value section

  {% if issue | linkedIssues("is caused by") %} {{ issue | linkedIssues("is caused by") | first | parentIssue | field("Epic Link") }} {% endif %}

• Add the Create issue post-function to the transition the Verify of the Bug workflow.

• Select Development from the Project field.

• Select Task from the Issue type field.

• Select duplicates in the Link to new issue section.

• Add an appropriate Summary (such as Duplicates - {{ issue.key}})

• Select the field Linked Issues from the Set fields of new issue section.

• Select Copy value from current issue from the drop-down.

• Add the post-function.