nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JSM import issues

Rob Peters

Hi,

We have implemented the following setup:

We have a JSM environment in which customers can report quality issues using the portal. Next to that we have many spaces in which we track and monitor our client projects, in these space we can also report quality issues as well.

Our quality manager want to be able to monitor and track all the quality issues from one environment, so i was wondering what are the possibilities to pull in issue created outside the JSM environment.

Currently when i edit a queue, the queue already filters only on the specific JSM space only.

Thanks.

Accepted answers

Sebastian Krzewiński

Hi @Rob Peters !

On JSM project queues you can't add more projects. What you can do is create dedicated dashboard and use there gadgets like filter results which can base on custom JQL.

Regards,

Seba

Matthew Sinclair

JSM queues are only designed for the space of which the queue lives. It's not like Kanban Boards or Dashboards at least for the time being.

As such I'd suggest using a Jira Kanban board or a Dashboard with a filter as they can be scoped to see any tickets across your site.

They can see JSM Tickets - but be prepared for the workflow not to play nice in the swimlane's as JSM isn't Jira in behaviorism.

I'd encourage you to have your site submit quality issues to one space - this would eliminate a lot of frustration potentially in your future.

Arkadiusz Wroblewski

Hi @Rob Peters

Another cool option is Jira Automation. You can set it up so that a new JSM request gets automatically made whenever there's a quality issue in a different project.

Just double-check that the new request has a proper Request Type, or else it might not show up in the customer portal.

https://support.atlassian.com/jira/kb/how-to-clone-an-issue-and-update-the-request-type-using-automation-in-jsm-cloud/

But remember, the two work items won’t automatically sync up.

Best,

Arek🤠🧙‍♂️

Mary Philip

Thanks a lot @Tintu Paul & @Rob Peters

I was searching for a similar use case as mentioned in the post. Realized Queues are available for JSM space only. It worked when I gathered all relevant issues in a dashboard using Filter gadgets. That helps!

Rob Peters

Hi Marry,

Thank you for sharing. A dashboard seems to be the work-around.

All comments

Sebastian Krzewiński

Hi @Rob Peters !

On JSM project queues you can't add more projects. What you can do is create dedicated dashboard and use there gadgets like filter results which can base on custom JQL.

Regards,

Seba

Matthew Sinclair

JSM queues are only designed for the space of which the queue lives. It's not like Kanban Boards or Dashboards at least for the time being.

As such I'd suggest using a Jira Kanban board or a Dashboard with a filter as they can be scoped to see any tickets across your site.

They can see JSM Tickets - but be prepared for the workflow not to play nice in the swimlane's as JSM isn't Jira in behaviorism.

I'd encourage you to have your site submit quality issues to one space - this would eliminate a lot of frustration potentially in your future.

Arkadiusz Wroblewski

Hi @Rob Peters

Another cool option is Jira Automation. You can set it up so that a new JSM request gets automatically made whenever there's a quality issue in a different project.

Just double-check that the new request has a proper Request Type, or else it might not show up in the customer portal.

https://support.atlassian.com/jira/kb/how-to-clone-an-issue-and-update-the-request-type-using-automation-in-jsm-cloud/

But remember, the two work items won’t automatically sync up.

Best,

Arek🤠🧙‍♂️

Tintu Paul

Hi @Rob Peters

May I check if the external project spaces you mentioned are inside the same Atlassian instance or hosted in an external environment?

If they are in the same instance, good news — custom JQL filters and a global Jira dashboard can definitely bring all your quality issues into one unified view for your Quality Manager.

For step-by-step guides on setting this up, please check out these official Atlassian articles:

Hope that helps! Feel free to update us on your progress, and good luck with the setup!

Mary Philip

Thanks a lot @Tintu Paul & @Rob Peters

Rob Peters

Hi Sebastian,

Thank you for your feedback! That is already my current work-around to get one overview with all Quality issues, but it would have been amazing to have the option to get them all in the JSM space.

Rob Peters

Hi Matthew,

Thank you for your feedback!

The one space setup would indeed make life simple, however it makes difficult to trace back where the Quality issue was raised/reported. In the current step all client project have a unique key which contains the project number. So if a quality issue is reported in a client project the key always tell the origin without filing any fields. It is also a limitation that you cannot link an issue to a space, it always have to be linked to an issue, if this would be possible that a one space setup would work.