Updating a ticket when the status of a Jira issue changes

<body>
<p id="docs-hc-snippet" style="display: none;">Jira can automatically update a Zendesk Support ticket linked to a Jira issue when the status of the issue changes in a Jira workflow.</p>
<div class="article-banners">
<div id="docs-wmp-link">
<a href="https://support.zendesk.com/hc/en-us/articles/5411234991258-plan" rel="noopener" target="_blank">What's my plan?</a>
</div>

<div class="article-banner" id="suite_all">
<table>
<tbody>
<tr>
<td>
<strong>All Suites</strong>
</td>
<td>Team, Growth, Professional, Enterprise, or Enterprise Plus</td>
</tr>
</tbody>
</table>
</div>

<div class="article-banner" id="support_all">
<table>
<tbody>
<tr>
<td>
<strong>Support</strong>
</td>
<td>Team, Professional, or Enterprise</td>
</tr>
</tbody>
</table>
</div>

</div>
<div id="docs-ai-summary">
<p id="docs-ai-summary-toggle">Summary: <span id="up-triangle">◀</span><span id="down-triangle">▼</span></p>
<p id="docs-ai-summary-content">You can configure Jira workflows to automatically update linked support tickets when issue statuses change. This includes adding internal or public comments, changing ticket status, and adding tags using post functions in workflow transitions. Dynamic placeholders allow personalized comments with issue, transition, and user details. This helps keep agents informed of issue progress and improves communication with customers.</p>
</div>

<div class="body">

<p class="p">Jira can automatically update a Zendesk Support ticket linked to a Jira issue when the status
of the issue changes in a Jira workflow.</p>
<p class="p">A <a class="xref" href="https://confluence.atlassian.com/adminjiracloud/working-with-workflows-776636540.html" target="_blank">Jira workflow</a> is the set of statuses and transitions
that an issue goes through during its lifecycle. You can configure a workflow to
automatically update a linked ticket after a Jira issue moves from one status to another in
the workflow.</p>
<p class="p">For example, after an engineer changes the Jira workflow status of an issue from "In
progress" to "Done," Jira can automatically add an internal note to the linked Zendesk ticket
notifying the agent. The agent can then notify the customer.</p>
<p class="p">Jira can also automatically notify the agent that a developer is now working on an issue by
adding an internal note to the ticket after the engineer changes the workflow status of the
issue from "To do" to "In progress."</p>
<p class="p">This article contains the following topics:</p>
<div class="p">
<ul class="ul" id="topic_tgc_fsr_zm__ul_vbq_2y5_1jb">
<li class="li"><a class="xref" href="#topic_th1_cpp_w4">Understanding how the ticket updates work</a></li>
<li class="li"><a class="xref" href="#topic_pjg_hpp_w4">Configuring a workflow to update tickets</a></li>
<li class="li"><a class="xref" href="#topic_zpg_fqp_w4">Changing the ticket update settings</a></li>
<li class="li"><a class="xref" href="#topic_if4_qmc_zhb">Supported comment placeholders</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title2" class="topic nested1" id="topic_th1_cpp_w4">
<h2 class="title topictitle2" id="ariaid-title2">Understanding how the ticket updates work</h2>
<div class="body">
<p class="p">Zendesk tickets are updated from Jira workflows using <em class="ph i">post functions</em>. Post functions
are a Jira workflow feature used to carry out additional processing after a workflow
transition is executed. For example, a post function can update the issue's fields after a
transition.</p>
<p class="p">Post functions are added to workflow transitions, not statuses. They run after the
transition is complete. Some post functions are essential and can't be deleted from a
transition or reordered. However, you can insert optional post functions between them. The
Zendesk integration adds "Notify Zendesk Ticket" to the list of optional post functions in
Jira.</p>
<div class="note" id="topic_th1_cpp_w4__note_mym_ynm_sxb">
<span class="notetitle">Note:</span>
<ul class="ul" id="topic_th1_cpp_w4__ul_prn_nrx_k3c">
<li class="li">Post functions can't solve tickets with empty required fields.</li>
<li class="li">Post functions don't support the inclusion of embedded images in Jira to be added as a
Zendesk internal note. </li>
</ul>
</div>
<p class="p">See the <a class="xref" href="https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/" target="_blank">Atlassian documentation</a> to learn more about post
functions.</p>
</div>
</div>
<div aria-labelledby="ariaid-title3" class="topic nested1" id="topic_pjg_hpp_w4">
<h2 class="title topictitle2" id="ariaid-title3">Configuring a workflow to update tickets</h2>
<div class="body">
<ol class="ol">
<li class="li">In Jira, click the Settings (cog) icon on the left sidebar, and select
<strong class="ph b">Issues</strong>.</li>
<li class="li">On the Issues page, select <strong class="ph b">Workflows</strong> from the left sidebar.<p class="p"><img alt="image" class="image img-screenshot" id="topic_pjg_hpp_w4__image_eh4_3w5_dgb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/jiracloud_workflows.png" width="600"></p>
</li>
<li class="li">Locate the workflow used to address issues linked to Zendesk tickets, and click
<strong class="ph b">Edit</strong> on the right side of the workflow.<div class="note">
<span class="notetitle">Note:</span> Jira doesn't let you edit a live
workflow. You must edit it in draft mode.</div>
</li>
<li class="li">In the <strong class="ph b">Transitions</strong> column, click the name of the transition you want to use to
trigger ticket updates.<p class="p"><img alt="image" class="image img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/jiracloud_workflow_transition.png" width="600"></p>
</li>
<li class="li">Click the <strong class="ph b">Post Functions</strong> tab, then click the <strong class="ph b">Add post function</strong> link on the
right.<p class="p"><img alt="image" class="image img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/jira3_workflow_add_post_fn.png"></p>
</li>
<li class="li">Select the <strong class="ph b">Notify Zendesk Support</strong> post function from the list and click
<strong class="ph b">Add</strong>.</li>
<li class="li">Configure the ticket update settings, then click <strong class="ph b">Add</strong>.<p class="p">You can change the ticket
status, add an internal or public comment, add tags, and include <a class="xref" href="#topic_if4_qmc_zhb">comment placeholders</a> in the comment
text.</p>
<p class="p"><img alt="image" class="image img-screenshot" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/jiracloud_workflow_config.png" width="600"></p>
<p class="p"><strong class="ph b">Note</strong>: Deleting
tags is not supported.</p>
</li>
<li class="li"> Next to the Zendesk Support post function, select the move down icon to move it
underneath the "Add a comment to an issue if one is entered during a transition" post
function.<br><img class="image img-screenshot" id="topic_pjg_hpp_w4__image_s32_lnc_pmb" src="https://zen-marketing-documentation.s3.amazonaws.com/docs/en/jiracloud_postfunction.png" width="600"><br>
</li>
<li class="li">Click <strong class="ph b">Publish Draft</strong> at the top of the page, then click <strong class="ph b">Publish</strong>.<p class="p">It's a
good idea to save a backup copy when prompted.</p>
<p class="p"><strong class="ph b">Important</strong>: Your changes
won't take effect until you publish the draft.</p>
</li>
</ol>
</div>
</div>
<div aria-labelledby="ariaid-title4" class="topic nested1" id="topic_zpg_fqp_w4">
<h2 class="title topictitle2" id="ariaid-title4">Changing the ticket update settings</h2>
<div class="body">
<p class="p">You can change the settings at any time.</p>
<ol class="ol">
<li class="li">In Jira, click the Settings (cog) icon on the left panel, and select <strong class="ph b">Issues</strong>.</li>
<li class="li">On the Issues page, select <strong class="ph b">Workflows</strong> from the left sidebar.</li>
<li class="li">Click <strong class="ph b">Edit</strong> on the right side of the workflow containing the transition you want
to edit.</li>
<li class="li">Select the transition and click the <strong class="ph b">Post Functions</strong> tab.</li>
<li class="li">Click the <strong class="ph b">Edit</strong> (pencil) icon on the right side of the post function that updates
the ticket.<div class="note">
<span class="notetitle">Note:</span> You can also delete the post function by clicking the delete (X)
icon.</div>
</li>
<li class="li">Make your changes, then click <strong class="ph b">Update</strong>.</li>
<li class="li">Click <strong class="ph b">Publish Draft</strong>, then click <strong class="ph b">Publish</strong>.</li>
</ol>
</div>
</div>
<div aria-labelledby="ariaid-title5" class="topic nested1" id="topic_if4_qmc_zhb">
<h2 class="title topictitle2" id="ariaid-title5"><strong class="ph b">Supported comment placeholders</strong></h2>
<div class="body">
<p class="p">You can enter dynamic content placeholders in the comment field of a post function. For
example, you can enter the following placeholder in the comment field of a Done transition
function:</p>
<pre class="pre">Issue {{issue.key}} has been resolved.</pre>
<div class="p">When the issue 'QA-4' transitions to the Done state, all linked tickets will be updated
with the following comment:<pre class="pre codeblock"><code>Issue QA-4 has been resolved.</code></pre>
</div>
<p class="p">For more information, see <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408887218330" target="_blank">Using placeholders</a>.</p>
<p class="p">The Zendesk JIRA integration supports issue-specific, transition-specific, and
user-specific placeholders. The placeholders are listed in the tables below. If placeholders
for user profile fields aren't rendering, check your <a class="xref" href="https://id.atlassian.com/manage-profile/profile-and-visibility" target="_blank">profile visibility settings</a> in Jira because many fields have
restricted visibility by default.</p>
<div class="p">
<div class="note">
<span class="notetitle">Note:</span> This integration does not support custom field placeholders.</div>
</div>
<div class="p">
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_if4_qmc_zhb__table_rvf_4nc_zhb" rules="all" summary="">
<caption><span class="tablecap"><span class="table--title-label">Table 1. </span><strong class="ph b">Issue-specific placeholders</strong></span></caption>
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry cellrowborder" id="d87e332" style="vertical-align:top;">Placeholder</th>
<th class="entry cellrowborder" id="d87e335" style="vertical-align:top;">Description</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.id</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Internal id number of the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.key</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue key. Example: QA-4</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.summary</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue summary</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.description</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue description</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.issuetype.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue type</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.issuetype.description</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue type description</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.creator.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">User name of the person who created the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.creator.emailAddress</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Email address of the person who created the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.creator.displayName</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Display name of the person who created the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.creator.timeZone</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Time zone of the creator</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.reporter.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Name of the person who reported the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.reporter.emailAddress</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Email address of the person who reported the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.reporter.displayName</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Display name of the person who reported the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.reporter.timeZone</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Time zone of the reporter</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.assignee.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">User name of the person assigned to the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.assignee.emailAddress</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Email address of the person assigned to the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.assignee.displayName</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Display name of the person assigned to the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.assignee.timeZone</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Time zone of the assignee</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.user.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Username of the user </td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.user.emailAddress</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Email address of the user</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.user.displayName</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Display name of the user</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.user.timeZone</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Time zone of the user</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.created</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Date and time the issue was created </td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.updated</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Date and time the issue was updated</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.priority.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue priority name</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.project.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue project name</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.project.key</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Issue project key. For example: QA</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.lastViewed</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Date and time the issue was last viewed</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.fixVersions.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Name of the fix version/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.fixVersions.description</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Description of the fix version/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.fixVersions.releaseDate</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Release date of the fix version/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.versions.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Name of the affected version/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.versions.description</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Description of the affected version/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.versions.releaseDate</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Release date of the affected version/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.components.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Name of the component/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.components.description</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Description of the component/s*</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.duedate</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Due date</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.timespent</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Time spent</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.timeoriginalestimate</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">The original estimated time required to resolve the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.resolution.name</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">A record of the issue's resolution</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.resolution.description</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">A complete description of the resolution</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.resolutiondate</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Date of issue resolution</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.watches.watchcount</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">The number of people watching the issue</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.labels</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">The label the issue relates to</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.environment</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">The hardware or software environment the issue relates to</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.fields.votes.votes</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">The number of votes an issue has</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e332" style="vertical-align:top;">issue.last_comment</td>
<td class="entry cellrowborder" headers="d87e335" style="vertical-align:top;">Last comment on the issue </td>
</tr>
</tbody>
</table>
</div>
</div>
<p class="p">*A comma-separated list if multiple items are selected.</p>
<div class="p">
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_if4_qmc_zhb__table_qrl_j4c_zhb" rules="all" summary="">
<caption><span class="tablecap"><span class="table--title-label">Table 2. </span>Transition-specific placeholders</span></caption>
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry cellrowborder" id="d87e796" style="vertical-align:top;">Placeholder</th>
<th class="entry cellrowborder" id="d87e799" style="vertical-align:top;">Description</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry cellrowborder" headers="d87e796" style="vertical-align:top;">transition.to_status</td>
<td class="entry cellrowborder" headers="d87e799" style="vertical-align:top;">The status an issue has transitioned to. For example: Done</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e796" style="vertical-align:top;">transition.from_status</td>
<td class="entry cellrowborder" headers="d87e799" style="vertical-align:top;">The status an issue has transitioned from. For example: In Progress</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e796" style="vertical-align:top;">transition.transitionName</td>
<td class="entry cellrowborder" headers="d87e799" style="vertical-align:top;">The transition name that occurred</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e796" style="vertical-align:top;">transition.workflowName</td>
<td class="entry cellrowborder" headers="d87e799" style="vertical-align:top;">The workflow name</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="p">
<div class="tablenoborder">
<table border="1" cellpadding="4" cellspacing="0" class="table" frame="border" id="topic_if4_qmc_zhb__table_d4k_s4c_zhb" rules="all" summary="">
<caption><span class="tablecap"><span class="table--title-label">Table 3. </span>User-specific placeholders</span></caption>
<colgroup>
<col>
<col>
</colgroup>
<thead class="thead" style="text-align:left;">
<tr class="row">
<th class="entry cellrowborder" id="d87e863" style="vertical-align:top;">Placeholder</th>
<th class="entry cellrowborder" id="d87e866" style="vertical-align:top;">Description</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry cellrowborder" headers="d87e863" style="vertical-align:top;">user.key</td>
<td class="entry cellrowborder" headers="d87e866" style="vertical-align:top;">Username of the person who caused the transition. This applies for Jira
Server users only.</td>
</tr>
<tr class="row">
<td class="entry cellrowborder" headers="d87e863" style="vertical-align:top;">user.displayName</td>
<td class="entry cellrowborder" headers="d87e866" style="vertical-align:top;">The user's display name. This applies to Jira Cloud users only.</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<script id="docs-schema-markup" type="application/ld+json">{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408832025114-Updating-a-ticket-when-the-status-of-a-Jira-issue-changes-Legacy",
"url": "https://support.zendesk.com/hc/en-us/articles/4408832025114-Updating-a-ticket-when-the-status-of-a-Jira-issue-changes-Legacy",
"headline": "Updating a ticket when the status of a Jira issue changes",
"description": "You can configure a Jira workflow to automatically update a linked support ticket with comments, status changes, and tags when the status of a Jira issue changes during its lifecycle.",
"articleSection": "Jira integration",
"datePublished": "2021-10-16T03:46:11+00:00",
"dateModified": "2026-04-30T17:08:08.817687+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/4408832025114-Updating-a-ticket-when-the-status-of-a-Jira-issue-changes-Legacy"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"url": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"url": "https://support.zendesk.com/hc/en-us"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk"
}
}</script><script id="ai-summary-script">
//<![CDATA[
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//]]>
</script>
</body>