Atlassian Marketplace Raledo Services Raise a Support Request
Apps
Jira is the ideal tool for collaboration between support agents and other teams in your organization. But it has it’s shortcomings. Agents can create linked issues in other team projects to delegate work to those teams. But sometimes agents have a difficult time tracking what is going on.
Linked Comments is an Atlassian Jira Cloud app that gives agents and collaborators the full context of any issue or request. It allows users to view all comments including those from linked issues without needing to open each linked issue.
With this add-on, agents will have greater awareness of what is happening in linked issues and will be better able to quickly resolve requests faster and more efficiently.
⚠️ User permissions are respected. Users will not see comments from linked issues unless they have permissions to see those comments.
Log into your Jira instance as a Jira Administrator.
Click the Apps dropdown and choose Find new apps.
The Find new apps screen loads.
Search for Linked Comments for Jira Cloud and click on the app tile.
The App Details screen loads.
Click Get app to start installing your app.
You're all set!
Click Close in the Installed and ready to go dialog.
<aside> ⚡ Linked Comments for Jira Cloud is built in Forge because we want to support Atlassian's new cloud app development platform that helps developers to build trusted and scalable apps with Atlassian-hosted compute and storage. Our team monitors the latest developments and releases from the Altassian Forge team and we will incorporate the relevant improvements and new capabilities as quickly as possible.
</aside>
As a user you need to grant access to the app. The first time you click the Linked Comments panel in the Issue Activity section, you will be presented with the following
Click Allow access. On the next screen you will be presented with a list of permissions. Please review these and if you have any questions please contact us. Linked Comments only requires read access to data and does not make any updates.
Click Accept.
The Linked Comments app will be activated. If there are any issues linked to the current issue that contain comments, they will be displayed.
Comments with a shaded background are comments that have been shared with internal Jira users. Unshaded comments have been shared with customers in a JSM project.
Clicking on the issue key reference in the comment footer will open the issue in a new tab. Clicking on the “Go to comment” link in the comment footer will open the issue in a new tab and scroll the page to make the comment visible.
There are two filter drop down lists - Link Type and Project. Selecting a Link Type or a Project from their respective lists will filter the list to show only comments matching the selection. After making a selection, click the search 🔍 button.
For example, select “is blocked by” link type will only show comments from issues that are linked from the current issue with the “is blocked by” link type. Similarly if you select project “Apollo” then only comments from linked issues in this project are displayed.
See Security and Privacy.
The app does not store any personal data.
One of the primary use cases is in a multi-tier, multi-team service organization. Usually these organizations have a Level 1 Customer Facing Service Desk, and a number of Level 2 teams (and possibly Level 3 teams).
When it is not possible for agents on the Level 1 service desk to resolve a customer’s request, a secondary ticket can be created and assigned to a Level 2 team. This team may have their own processes and will want to add their own comments the secondary ticket created
The L1 agent has limited visibility into the L2 teams and their tickets. The original customer request is linked to the L2 ticket and the L1 agent can see the status of the L2 ticket.
But using Linked Comments the agent can now also see the comments added to the L2 ticket and can monitor progress more closely. This is also useful from an audit and tracking perspective since we can read the full history of the parent ticket and all its related tickets. The more context the agents have the more productive and effective they will be in communicating with their customers.
Another advantage is that the L2 agents do not need to switch to the original ticket to add comments. They know that the L1 agent can see what is going on.
The above can be generalised to any set of teams using issue links to create relationships between issues to enable them to collaborate.
We are considering the following in our roadmap. Please let us know what features you would like to see [support link].