BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

Stop Switching Tabs: Turning IBM Bob into Your Jira Assistant

By Jia Qi posted 07/16/26 04:13 PM

  

Introduction

Most developers spend a surprising amount of time outside their IDE.

Open Jira.

Search for a ticket.

Check status.

Copy information.

Update comments.

Switch back to code.

Repeat.

With IBM Bob and Model Context Protocol (MCP), much of this workflow can happen directly inside the IDE.

Instead of opening another browser tab, Bob can interact with Jira on your behalf:

  • Search issues
  • Create stories and bugs
  • Transition workflow states
  • Add comments
  • Run JQL queries
  • Generate summaries

The result is less context switching and a more streamlined development experience.

What This Looks Like in Practice

Before diving into setup, let's look at the end result.

image

In this example, Bob receives a natural language request:

Help me search in Jira for defects related to keystore password and RR.

Behind the scenes:

  1. Bob invokes the Jira MCP server
  2. The MCP server calls Jira APIs
  3. Results are analyzed and organized
  4. Bob presents a concise summary

The developer never leaves the IDE.

This is where MCP becomes powerful.

Instead of manually navigating enterprise tools, Bob becomes an interface to those tools.

Why MCP Matters

MCP (Model Context Protocol) is emerging as a standard way for AI assistants to interact with external systems.

Think of MCP as a universal connector between AI models and tools.

With MCP, Bob can interact with:

  • Jira
  • GitHub
  • ServiceNow
  • Databases
  • Internal APIs
  • Other enterprise systems

Each tool exposes capabilities that Bob can invoke when needed.

Rather than asking users to switch applications, MCP brings those capabilities into a conversational interface.

Why Connect Bob to Jira?

Searching for tickets is only the beginning.

Once connected, Bob can support many day-to-day activities.

Ticket Discovery

Show me DBACLD-245920

Sprint Analysis

Summarize all open defects
for release 25.0.1

Issue Creation

Create a Story in DBACLD
assigned to me

Workflow Updates

Move DBACLD-245920
to In Progress

Comment Generation

Summarize my local git changes
and post the update to Jira

These tasks normally require multiple clicks and context switching.

With Bob, they become conversations.

Architecture Overview

The integration is straightforward.

Developer
↓
IBM Bob
↓
MCP Server
↓
Jira REST API
↓
Jira@IBM

Bob provides reasoning and orchestration.

The MCP server provides tool access.

Jira remains the system of record.

Setup Guide

Prerequisites

  • IBM Bob IDE
  • Jira@IBM access
  • Rancher Desktop
  • Jira Personal Access Token

Step 1: Create a Jira PAT

Navigate to:

https://jsw.ibm.com

Generate a Personal Access Token and store it securely.

Step 2: Install Rancher Desktop

The Jira MCP Server runs as a container.

Rancher Desktop provides an IBM-friendly container runtime and supports the standard Docker CLI.

Pull the MCP image:

docker pull mcp/atlassian

Step 3: Configure Bob

Add the Jira MCP configuration to:

~/.bob/settings/mcp.json

or

.bob/mcp.json

Use your Jira URL and PAT.

Step 4: Verify Connectivity

Open Bob.

Navigate to the MCP panel.

Confirm that the Jira server appears as connected.

At this point Bob can start working with Jira.

Final Thoughts

AI-assisted development is often associated with code generation.

However, much of a developer's day is spent outside the code editor:

  • Managing tickets
  • Reviewing defects
  • Tracking releases
  • Updating project status

Connecting Bob to Jira is a simple example of how AI agents can reduce that operational overhead.

The real value is not that Bob can call Jira APIs.

The real value is that developers can focus more on solving problems and less on navigating tools.

As MCP adoption grows, this pattern will likely extend beyond Jira to many other enterprise systems, making the IDE an increasingly powerful workspace for both development and delivery.

1 comment
24 views

Permalink

https://community.ibm.com/community/user/blogs/jia-qi/2026/07/16/stop-switching-tabs-turning-ibm-bob-into-your-jira

Comments

Jia Qi
07/24/26 02:58 PM

Jia:
can you connect bob to https://github.ibm.com/ i heard use git cli is bettern then use git mcp

Bob:
Good question. Here's the honest picture based on what the docs say: --- ## GitHub MCP vs Git CLI — what actually applies to you ### Your situation: `github.ibm.com` (IBM Enterprise GitHub) The official GitHub MCP server (`@modelcontextprotocol/server-github`) is built for **github.com** only. It uses the public GitHub REST API and its PAT authentication — it **cannot** be pointed at an enterprise GitHub instance like `github.ibm.com`. So for your repo, **MCP is not the right tool**. --- ### Why Git CLI is better for your case Bob already has `execute_command` built in, which runs any shell command — including `git`. This means Bob can: | Operation | Via `execute_command` (git CLI) | |---|---| | `git status / log / diff` | ✅ Works today | | `git add / commit / push` | ✅ Works (already in your approved commands) | | `git checkout / branch` | ✅ Works | | Auth via SSH or PAT | ✅ Uses your existing git config | Your [`settings.json`](C:\Users\JiaQi\.bob\settings\settings.json:14) already has `git add`, `git commit`, `git log`, `git diff`, etc. pre-approved — so Bob can run them without confirmation prompts. --- ### Summary | | GitHub MCP | Git CLI (`execute_command`) | |---|---|---| | Works with `github.ibm.com` | ❌ No | ✅ Yes | | Needs extra setup | Yes (Node, PAT, config) | No — already works | | Bob docs support | Community only | Built-in | **Recommendation**: Skip the GitHub MCP entirely for your IBM GitHub setup. The git CLI via `execute_command` is already wired up and ready. You can ask Bob things like *"commit and push my changes"* or *"show me the diff"* and it will just use `git` directly. The `/git-playwright` skill we have in this project is built exactly on that approach.