Jira - JSM integration and Centralized Reporting

Subhajit Ghosh_kt3ze2

Our organization is gearing up to integrate Jira Service Management (JSM) into our IT Operations Change Management framework. Up to this point, we've relied on Jira for Change management, but we've encountered its limitations over time. To expedite the adoption of JSM, our leadership has decided to utilize Jira for initiating Change tickets. Upon the creation of a Jira ticket, automated processes will generate corresponding JSM tickets. Once the JSM ticket is generated, the previously created Jira ticket will be locked to prevent further modifications, rendering it inactive.

Now, I have a couple of questions:

1. Has anyone in this community attempted a similar approach? If so, what was the overall experience?
2. Given that each engineering team manages its own projects, how can we implement centralized reporting, ensuring all change requests are consolidated for comprehensive visibility

Dave Rosenlund (Trundl)

Hi, @Subhajit Ghosh 👋

I cannot speak to #1, however I have some advice for #2.

To effectively manage a portfolio of projects (aka PPM), you'll want to learn about 'Advanced Roadmaps' (from Atlassian). This feature of Jira is specifically designed for working across teams/projects.

That said, that feature was designed more for planning than reporting. In my experience, those who use AR find it lacking when it comes to reporting or managing in-flight projects.

Inevitably, those who find it lacking use some combination of Atlassian Marketplace products to handle their PPM needs. Here are some of them, but that link only searches for PPM. You may want to take a deeper look yourself.

Hope this helps,

-dave