Relationship between JSM Bug Report and Jira Software
Asked by Guy Renko:

I tried to search for this but I'm not really sure what I'm even trying to ask. I'm just going to type and edit and hope the question makes sense at the end.

We have a Service Management portal to report bugs in our in-house ERP but then they are just issues in JSM.

Some background. I'm the JSM admin here and have pretty good knowledge of everything JSM and automations. I'm relatively new to Jira Software but love that many of the settings concepts are very similar. We are on the Standard Plan in JSM and free plan on Jira Software. All projects are Company-Managed and I have full access to everything.

We can of course assign the head developer to deal with that issue but shouldn't we be putting the bug into Jira software as well so that they can be timeline'd plus we have agents in Jira Software that are not agents in Jira Service Management.

How is this typically managed?

I've seen some "apps" that can replicate issues back and forth between projects but I think the "end user"/reporter does need to be part of 90%+ of the comments made on that bug issue in Jira Software.

Just trying to understand best practices. Any input or links is greatly appreciated.


Answers:
author: Matthias Gaiser _K15t_
body: Hey [@Guy Renko](/t5/user/viewprofilepage/user-id/5161018)

I think you expressed yourself in an understandable way ?

Based on your explanations, I assume you're having JSM and Jira Software in the same Jira instance, right? (aka the base url xxx.atlassian.net is the same).

There are different scenarios possible:

* **Collaborate in JSM**   
  If you're in the same instance, then your developers can join the JSM projects without consuming an additional JSM license as collaborators and comment on the JSM issues internally, see also [these docs for clarifying the project roles](https://support.atlassian.com/jira-service-management-cloud/docs/what-users-and-roles-are-there-in-jira-service-management/).  
  I'd recommend to use this more when you need some development support for a quite technical support ticket.
* **Create and Link Issues**   
  Whenever you encounter an actual bug, you can create a bug in Jira Software and [use issue links](https://support.atlassian.com/jira-service-management-cloud/docs/link-subtasks-issues-and-pages-from-the-new-issue-view/#Link-issues) to connect the bug and the support ticket (or maybe multiple support tickets). Using that link, you can clearly separate the customer communication from the communication around fixing the bug - and Jira's view always shows you at least the status of the issue in the issue link section.  
  You can also automate some parts of this step.
* **Sync Issues**   
  A step further, you can also synchronize specific JSM issues with your Jira Software project using [an issue sync app](https://marketplace.atlassian.com/search?query=issue%20sync). There you can configure exactly which issues and which fields of the issues to synchronize. In addition, you can define which comments (public/private) you'd like to sync.  
  Please note that I'm part of the team behind such an issue sync app, [Backbone Issue Sync](https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira?hosting=cloud&tab=overview). [Here's an example](https://help.k15t.com/backbone-issue-sync/5.9/cloud/2nd-level-support-jira-service-management-to-jira) how that can look like with Backbone.

Hope that helps to get you started in your "collaboration design process".

Cheers,  
Matthias.

comments: author: Guy Renko
body: Was going through my previous posts and don't know what happened to my response.

Thank you for all the info. I remembered reading about Collaborators as soon as you mentioned it and Backbone Issue Sync is the app I was referring to. Thank you again!


author: Hannes Obweger - JXL for Jira
body: Hi [@Guy Renko](/t5/user/viewprofilepage/user-id/5161018)

just to add to [@Matthias Gaiser _K15t_](/t5/user/viewprofilepage/user-id/853318)'s great answer: If the **issue linking** approach (#2 in Matthias' list) is an option for you, perhaps the app that my team and I are working on might be of interest to you: [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2653824).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including all JSW and JSM specific fields - much like you'd do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) *issue hierarchies.*These issue hierarchies can be based on Jira's built-in parent/child relationships (like task/sub-task), and/or based on issue links of configurable issue link types.

With this, you can build a cross-JSM/JSW view like e.g. this in just a couple of clicks:

![jsm-jsw-overview.gif](https://community.atlassian.com/t5/image/serverpage/image-id/315120i5A323AD96941C678/image-size/large?v=v2&px=999 "jsm-jsw-overview.gif")

As you can see above, the requests from JSM are listed together with their linked bugs in JSW, giving an easy-to-comprehend overview of the work and progress across the involved teams. Note that this is really just one of a virtually endless of number of possible views and reports in JXL; you can also e.g. *group* your issues by any issue field(s), calculate *sum-ups* , and freely configure *conditional formatting* rules.

Any questions just let me know,

Best,

Hannes

comments: author: Guy Renko
body: Thank you for the additional information. I love all the inline edit in JXL.


Tags: cloud

jira-service-management

jira-service-management-cloud