Is it possible to have JSM Request tickets to show on an existing project/board ?

[Joao Borges]

Hi there,

I am trying to have all my JSM Requests to go to an existing board in Production, which is already linked to another JIRA project called TECHNOLOGY

So, what I had in the past was the following:

JSM  Request > "TEMPORARY BOARD"  > AUTOMATION RULES  ( to clone/create tickets) > PRODUCTION BOARD

---

Goal:

JSM Request > Production Board

---

We are trying to eliminate this temporary board + automation rules, it can be more complicated in terms of linking tickets, keeping status in sync and more maintenance. 

Do I just have to  modify the JQL Board rules for the existing Project ? Also, do I need to update the workflow on JSM project to be the same as the Production board workflow ?

I appreciate any help

Thanks,

[Alex Koxaras _Relational_ · Accepted solution]

Hi @Joao Borges 

In my opinion, and from what I've read (and if I understand correctly your need), there is no need to clone the tickets to a new project. You can simply create a new board by creating a new JQL which will hold all the issues you want (jsm tickets, plus technology). Then you can map all available statuses to your board columns. If you find the need to create new columns, then be my guest! :)

Let me know if all the above is crystal clear.

Alex

[Joao Borges]

Alex, 

We do not want to create a new board, we want requests from Jira Service Management to go to an existing Production Jira software called Technology.

There is a board there already

[Alex Koxaras _Relational_]

Then change the existing board filter to include the JSM issues and map the workflow statuses to the existing columns.

[Joao Borges]

@Alex Koxaras _Relational_  In another words, i would need to modify the workflow under issue type to point to TECHNOLOGY project ? or just map the JSM statuses on the the existing TECHNOLOGY BOARD 

Board Settings > Columns>  add each status to each column

Thanks for the help

[Alex Koxaras _Relational_]

You need to:

• modify the JQL filter of the board to include the JSM issues (and when you do that)
• map the new statuses (which will come from the workflows associated with all issue types in the JSM project) to the existing production board

[Joao Borges]

@Alex Koxaras _Relational_  Understood, but do I need to change the workflow on the issuetype itself ?

[Alex Koxaras _Relational_]

No, there is no such need. I mean is not mandatory to change the workflow. You only have to map the statuses to the board columns, in order to see the issues in the various new statuses which are not represented by any column on the board.

[Jack Brickey]

You can certainly include JSM issues on your JSW project board if that is your goal. You simply need to edit the underlying board filter to include the desired issues. The question I would have to be able to comment further is how would you identify the specific JSM issues to include on the board such as label status etc.

[Joao Borges]

Jack, sorry but did not understand the second part .

Yes, by editing the JQL query I should be able to see all the tickets, but it will also depend on issue status.

Do I need to change the workflow for JSM requests as well ?

[Jack Brickey]

Sorry for the jumbled post it was resulting from dictation. I have corrected in the point is do you want all JSM issues from the project to appear or just certain ones? If certain ones how are they identified?

You don't need to necessarily change your JSM workflow. However, mixing two completely different workflows on a single board can get a bit messy. It comes down to how the two workflows map to the columns to present a clean solution.

Finally it might be a better solution if you only want a few JSM tickets to appear on the board to simply create linked issues in your jira software project.

[Vijay Byndoor]

Question:  will this work even if the Jira and JSM are running on different data center instances