Migrating Jira tickets (signifying a post mortem) into JSM/OpsGenie
Asked by Ken Young:

Hi All,

We utilzied a Jira project to manage our postmortems when we were a PagerDuty. Now that we have invested into JSM/OpsGenie, we would like to migrate our history (i.e. the tickets) into JSM and into OpsGenie. Currently the reporting in OpsGenie isn't very configurable, so wondering if others have migrated Jira Tickets to JSM, and how the OpsGenie/JSM sync'ing is best set up going forward so we can continue to report out via Jira's Dashboards?


Answers:
author: Nick H
body: Hi [@Ken Young](/t5/user/viewprofilepage/user-id/2245441) ,

You can certainly move issues from one project (Jira) to another (JSM). A few things to consider when doing this;

1 - When moving issues from one board to another, the webhook request is updated vs. created. You can also decide whether this moves the issues back into an Open state, remains Done/Closed/Resolved, etc.:

![bulkcomm1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143013iCA434EC13A927736/image-size/large?v=v2&px=999 "bulkcomm1.jpg")

2 - \^ I point this out because the JSM integration by default will create Opsgenie alerts when the webhook event is create. Again - since the webhook event transitioning issues from one project to another is updating them, this would need to be factored into the move.

You'd then need to adjust what issues are going to create alerts in Opsgenie. Based on the log above, I'd want one of my integration's Create Alert actions to filter on these fields:

![bulkcomm2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143014iBAC7349AF096CE5A/image-size/large?v=v2&px=999 "bulkcomm2.jpg")

The fields you filter on would be dependent on what the issues are being transitioned into. This would essentially determine the sync'ing you mentioned.

To complete a bulk move - and transition issues from a one project to another - I've included a recording and screenshots below to provide a better visual.

**Recording:** <https://www.screencast.com/t/htzG4MdWkUHY>

**Screenshots:**

![bulkcomm3.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143018i5994B1349715FC5B/image-size/large?v=v2&px=999 "bulkcomm3.jpg")![bulkcomm4.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143017i3C2DB20B88F95ACF/image-size/large?v=v2&px=999 "bulkcomm4.jpg")![bulkcomm5.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143019i634C47C1B3AD5618/image-size/large?v=v2&px=999 "bulkcomm5.jpg")![bulkcomm6.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143020i7B45F129C83E69D6/image-size/large?v=v2&px=999 "bulkcomm6.jpg")![bulkcomm7.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143023i16732B23EAEDEE7B/image-size/large?v=v2&px=999 "bulkcomm7.jpg")![bulkcomm8.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/143022i5C4CE65C0837EDFC/image-size/large?v=v2&px=999 "bulkcomm8.jpg")

Another thing to consider as well related to reporting; Moving all these issues from one project to another - then into Opsgenie - might not get the full value of some of our reports such as the MTTA/R report - which measures ack and close time.

If you have hundreds of issues as well, it might make sense to break the bulk move into batches to avoid any rate limiting.

Again, not sure the value is there since this transition is from one system (PD) \>\> to another (OG). But I hope this helps if you are still considering moving everything into Opsgenie, and need these in your account.

I've also included some links to docs below for things that are related to what is shared above.

Let us know if you have any additional questions, or if you were looking for something else.

-Nick

JSM Integration: <https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-jira-service-management/>

MTTA/R Report: <https://support.atlassian.com/opsgenie/docs/view-global-alert-mttar-analytics/>

\^ other reports can be viewed on the right side of that page.

Bulk Moving Issues: <https://confluence.atlassian.com/jiracoreserver/editing-multiple-issues-at-the-same-time-939937916.html>


Tags: jira-service-management