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; } } }

How to link existing Projects/Boards to a new JSM project

Joao Borges_ch4uwn

Hi there

I am new to JSM and trying to link an existing board from a different project, to our new JSM service PROJECT.

So the team will create a ticket using the new tool, JSM. JSM project will be linked to an existing project from JIRA Software. (TECHNOLOGY); and as soon as a ticket gets created, it will appear on TECH KANBAN board

Is it possible do link a JSM service to an existing JIRA Software service ?Or I would need to create a brand new board ?

Thanks,

Accepted answers

All comments

Melo_45tw58

Hi Joao,

You can add the new JSM project to your existing board. If you're are familiar with JQL, it can be straightforward.

Here is how to edit a board filter:
https://support.atlassian.com/jira-software-cloud/docs/configure-filters/#Editing-a-board--x27-s-filter

A caveat, to transition and edit issues from the JSM project, you will need to be a JSM agent.

I hope that helps, let me know if you need help with the filter.

Cheers,

Melo

Joao Borges_ch4uwn

@Melo I do not what to change the current board jql filter. I want to link the JSM project to this board. So if someone makes a request on JSM, it will appear on JIRA SOFTWARE board

Joao Borges_ch4uwn

Any update on this question ?

Melo_45tw58

Hi Joao,

I don't think there is another way around it. What defines the issues displayed on boards are the filters. I would suggest you do a test on a different board.

On the board, filter add a JQL like "project in (TECHNOLOGY, JSM, "any other project key")" that may help you to understand the concept.

Thanks,

Melo

Daniel Ebers

Hi @Joao Borges

what @Melo describes is the way that I would also have recommended intuitively.
It is just what is done in Jira for requirements like the one you discussed here.

Of course, you could bring in Automation (it is free and ready to use in your instance) but it will not address the requirement as you explained. Rather you use this way normally to create a clone of a created issue in a different project - OR - to create a new issue in a different project and link both.

Here are some more information and inspiration:
https://www.atlassian.com/software/jira/features/automation

Again, for the exact requirement I'd suggest the implementation of Melo.

Regards,
Daniel

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management