View as Markdown
Jira icon

Jira ACTION

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation
  • Action
  • Writes data
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Jira account once, then configure and run Add Watcher To Issue from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "jira-add-watcher-to-issue",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    issueIdOrKey: "Issue ID or Key",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Add Watcher To Issue inputs
Property Type Description
cloudId Cloud ID string
The Jira Cloud site ID (for example, 11223344-a1b2-3b33-c444-def123456789). Use Get Cloud ID to discover IDs. See the documentation
Required Dynamic
issueIdOrKey Issue ID or Key string
The ID or key of an issue
Required Dynamic
accountId Assignee ID string
The account ID of the user, which uniquely identifies the user across all Atlassian products, For example, 5b10ac8d82e05b22cc7d4ef5
Required Dynamic

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
jira-add-watcher-to-issue
Version
0.0.25
App
Jira
Authentication
OAuth
Read-only
No
Destructive
No
Open world
Yes