Skip to content
Help Center
Submit a request Sign in

Use Jira-linked case history and send engineering comments

One engineering issue can affect several customers, while each customer still needs its own support conversation and next update. The Supportbench integration lets an authorized Jira user inspect linked case history from the Jira issue. Use this guide to select the right case and read its evidence. For creating or linking issues from Supportbench, use the companion operations guide; for installing and authenticating the integration, use the configuration reference.

At a glance

For: support agents, engineering collaborators and integration administrators. Applies to: Supportbench Core.

Start here: Jira → open the issue → Supportbench tab

Choose the right Jira workflow  ·  Before opening customer history in Jira  ·  Read a linked case step by step  ·  Understand what Include Jira comments does  ·  Send an engineering comment from the Supportbench case  ·  Keep ownership clear across several customer cases  ·  Verify the integration result  ·  Troubleshoot missing or unexpected history

Choose the right Jira workflow

You need to…Start here
Read customer evidence while working a Jira issueFollow this article: open the Supportbench tab, select a Linked case and refresh its history.
Link an existing issue or create one from a support caseUse the current Jira operations guide linked below. Confirm the correct case and Jira project before making the link.
Set up the integration or investigate credentialsUse Configure Jira case integration. An issue-history viewer is not an integration setup screen.
Decide how Jira status changes affect support workReview the Jira operations and configuration guides with the support process owner. Do not assume a Jira status resolves every linked customer case.

A Jira issue represents engineering work. A Supportbench case represents the customer’s support request, including its own conversation, ownership and service commitments. Linking the records makes context available; it does not eliminate the need to communicate with each customer.

Before opening customer history in Jira

  1. Confirm the Supportbench integration is installed and configured for the intended Jira environment. The Jira administrator may need to enable the app or troubleshoot its installation.
  2. Confirm that the Jira issue is linked to the relevant Supportbench case. If there is no link yet, an authorized support agent can follow the link/create procedure in the companion guide.
  3. Identify the exact issue key and the case you expect to see. Similar issue titles are not proof that two customer incidents have the same cause.
  4. Use the account and permissions intended for this work. The integration rechecks the issue-to-case relationship when reading history; having a copied case identifier does not establish that it belongs to this issue.
  5. Review customer information according to your organization’s engineering-access policy. Do not copy private case details into a broader Jira audience merely because a linked history view is available.

The issue’s compact Initial Supportbench Case panel can provide a starting case link. When you need the issue’s linked-case selection and history, use the Supportbench issue tab. The tab’s placement may depend on the Jira issue layout configured by your administrator.

Read a linked case step by step

  1. Open the intended Jira issue and confirm its key and summary. Find the Supportbench issue tab.
  2. In Linked case, choose the customer case you intend to inspect. If several cases share the issue, deliberately choose one rather than assuming the first case represents every affected customer.
  3. Choose whether to enable Include Jira comments. Use it when Jira-comment activity is relevant to the combined history; leave it off when you want to focus on the other case activity.
  4. Choose Refresh to load the selected history and option state.
  5. Read Case history. Check the reported symptoms, work already attempted, dates and customer-specific details. Distinguish a recorded fact from an assumption or proposed fix.
  6. Open the displayed Supportbench case link when you need the full conversation, attachments or the normal case workspace. Review the case there before taking a support action.
  7. Repeat for another Linked case when you need to compare affected customers. Record meaningful differences rather than copying the first customer’s conclusion to all cases.

Expected result: the history corresponds to the case you selected and the Include Jira comments option you chose. Verify the case identifier before using the evidence in an engineering decision. The compact panel is not a substitute for the full case conversation or attachments.

Understand what Include Jira comments does

Include Jira comments controls whether Jira-comment activity is included in the displayed history. It is a reading option. This history surface does not provide a verified procedure for replying to a Jira comment as if it were an ordinary Supportbench activity.

To communicate with the customer, return to the Supportbench case and use its normal reply workflow after checking recipients and visibility. To add engineering discussion, use the separate Comment action on a linked Jira item in the Supportbench case, described below, or the appropriate Jira issue action. Whether Jira comments are also brought into Supportbench depends on the configured integration behavior, including Automatic Jira activities; ask the administrator to check the current configuration reference.

Do not assume that selecting the checkbox sends a message, imports every historic comment again, or changes the customer’s visibility. Reading a combined timeline and configuring comment synchronization are different tasks.

Send an engineering comment from the Supportbench case

The Jira issue history tab is a reading surface, but the Supportbench case has a separate command for posting an engineering comment to a linked Jira issue. Use this when you need to add a verified reproduction detail or ask the engineering team a question without leaving the case. It is not a customer reply.

  1. Open the intended Supportbench case and choose its Actions tab.
  2. Find the linked Jira item and confirm the issue key. Select Comment when available. The command depends on the enabled provider and permission to comment; ask the integration administrator if it is missing.
  3. In the Comment on JIRA dialog for that issue, enter the message in Comment. Jira comments send plain text. Add images and files directly in Jira when needed.
  4. Check that the wording is suitable for the Jira issue’s audience. Include the relevant verified test and result, without unnecessarily disclosing private customer details.
  5. Choose Send comment and wait for the result. Open the Jira issue and verify the posted comment before retrying an ambiguous response.
  6. If the customer also needs an update, send a separate reviewed reply through the case’s normal customer communication workflow.

For example: “On case c-EXAMPLE, the reset reproduced on the tested controller version after the diagnostic sequence recorded in the case. Can you confirm whether the proposed fix covers this version?” Replace the example with verified details. Do not state that a fix is deployed or that all linked customers are affected without evidence.

Keep ownership clear across several customer cases

DecisionRecommended practice and reason
Who owns the customer update?Keep a named support owner and next update on each case. Engineering progress alone does not tell every customer what happens next.
Which evidence belongs on the issue?Summarize the common defect and retain case-specific evidence where authorized. Note differences such as version, equipment or reproduction conditions.
When is a fix ready to communicate?Verify the release or remediation evidence and whether it applies to each customer. A changed issue status is not sufficient proof of deployment.
Can several cases close together?Use the established case-resolution process. Confirm customer impact and service commitments individually; linking an issue is not a blanket closure instruction.
What belongs in reusable knowledge?Once validated, capture the common symptoms, scope and resolution in a reviewed article, with customer-specific information removed.

Example: recurring equipment fault

Three customers report intermittent pump-controller resets. Their cases link to one Jira issue. In Linked case, compare the controller versions and recorded conditions for all three. Engineering confirms a fix for one firmware range. The support owners verify applicability separately, agree each customer’s next action, and keep their own case history current. The linked issue coordinates the technical work without merging the customers’ conversations.

Verify the integration result

  1. Select a known linked case and confirm its identifier in the history.
  2. Choose another linked case, if available, and Refresh. Confirm that the displayed conversation changes to that case.
  3. Toggle Include Jira comments and Refresh. Check an activity known to be a Jira comment rather than assuming every visible message is one.
  4. Open the case link and compare a relevant recent activity with the Supportbench workspace. Use the full workspace for attachments and support actions.
  5. If the result is incomplete or unavailable, capture the issue key, selected case, option state, time and visible error without including unnecessary customer content.

These checks verify the reading workflow. They do not prove every configured synchronization rule, status action or future event delivery. Test those separately when the integration configuration changes.

Troubleshoot missing or unexpected history

ProblemLikely cause and corrective action
No Supportbench tab appearsAsk the Jira administrator to check app installation, issue layout and the intended Jira environment. Do not recreate the integration blindly.
Linked case is empty or the expected case is missingConfirm the case was linked to this exact issue and that the integration can read the relationship. Use the Supportbench link/create workflow to inspect it.
History belongs to a different customerCheck Linked case and Refresh. Several customer cases can share one issue; a matching issue title does not select the right case for you.
A Jira comment is missingEnable Include Jira comments and Refresh. If it still does not appear, check whether the relevant comment activity exists and whether the integration’s automatic-activity setting applies.
The latest activity is not visibleRefresh, then compare the full Supportbench case. Investigate synchronization or access errors instead of repeatedly relinking the same issue.
Attachments are neededOpen the full Supportbench case. The compact issue panel directs you to the case activity/history for the complete conversation and attachments.
You cannot reply from the history viewThis is a history-reading surface. Use the normal Supportbench customer reply or Jira issue comment action, with the appropriate audience.
An authorization or integration error appearsConfirm the intended Jira installation and Supportbench account with the administrator. Provide the issue key, case ID, time and exact error; never send API tokens in a support screenshot.

Was this article helpful?