Jira Comments & Worklogs

Comments, worklogs, changelogs, and user profiles

Add Comment

Add a comment to a Jira issue.

This is a write tool. Disabled when READ_ONLY_MODE=true.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’, ‘ACV2-642’)
body	string	Yes	Comment text in Markdown format
visibility	string	No	(Optional) Comment visibility as JSON string (e.g. ‘{"type":"group","value":"jira-users"}’)
public	boolean	No	(Optional) For JSM/Service Desk issues only. Set to true for customer-visible comment, false for internal agent-only comment. Posted via the ServiceDesk API as a raw string; Jira Cloud renders it server-side and stores ADF (markdown observed to render on Cloud, without the client-side markdown-to-ADF guarantees of the regular comment path). Cannot be combined with visibility. If the issue’s project is listed in JIRA_INTERNAL_ONLY_PROJECTS, only public=false is accepted — public=true or omitting this field is rejected. Issues in such a project that are not JSM customer requests (e.g. an agent-created Task) have no portal audience and are exempt: they post through the ordinary comment path and ignore this field.
Example:

{"issue_key": "PROJ-123", "body": "## Investigation\n\nFound the root cause in module X."}

Supports Markdown formatting. On Jira Cloud, mention users with [~accountid:ACCOUNT_ID] or @[Display Name](accountid:ACCOUNT_ID). Use visibility parameter for restricted comments (e.g., service desk internal notes). The generated schema lists body, but callers may use comment as an equivalent input alias for the same comment text.

---

Edit Comment

Edit an existing comment on a Jira issue.

This is a write tool. Disabled when READ_ONLY_MODE=true.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’, ‘ACV2-642’)
comment_id	string	Yes	The ID of the comment to edit
body	string	Yes	Updated comment text in Markdown format
visibility	string	No	(Optional) Comment visibility as JSON string (e.g. ‘{"type":"group","value":"jira-users"}’)

---

Get Worklog

Get worklog entries for a Jira issue.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’, ‘ACV2-642’)

---

Add Worklog

Add a worklog entry to a Jira issue.

This is a write tool. Disabled when READ_ONLY_MODE=true.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’, ‘ACV2-642’)
time_spent	string	Yes	Time spent in Jira format. Examples: ‘1h 30m’ (1 hour and 30 minutes), ‘1d’ (1 day), ‘30m’ (30 minutes), ‘4h’ (4 hours)
comment	string	No	(Optional) Comment for the worklog in Markdown format
started	string	No	(Optional) Start time in ISO format. If not provided, the current time will be used. Example: ‘2023-08-01T12:00:00.000+0000’
original_estimate	string	No	(Optional) New value for the original estimate
remaining_estimate	string	No	(Optional) New value for the remaining estimate

---

Batch Get Changelogs

Get changelogs for multiple Jira issues (Cloud only).

Parameters:

Parameter	Type	Required	Description
issue_ids_or_keys	string	Yes	Comma-separated list of Jira issue IDs or keys (e.g. ‘PROJ-123,PROJ-124’)
fields	string	No	(Optional) Comma-separated list of fields to filter changelogs by (e.g. ‘status,assignee’). Default to None for all fields.
limit	integer	No	Maximum number of changelogs to return in result for each issue. Default to -1 for all changelogs. Notice that it only limits the results in the response, the function will still fetch all the data.
Example:

{"issue_keys": ["PROJ-1", "PROJ-2", "PROJ-3"]}

Efficient for tracking field changes across multiple issues at once. Returns change history for each issue.

Only available on Jira Cloud.

---

Get User Profile

Retrieve profile information for a specific Jira user.

Parameters:

Parameter	Type	Required	Description
user_identifier	string	Yes	Identifier for the user (e.g., email address ‘[e-mail]’, username ‘johndoe’, account ID ‘accountid:…’, or key for Server/DC).

---

Search Assignable Users

Search Jira users assignable in a given project or issue.

Parameters:

Parameter	Type	Required	Description
query	string	Yes	Free-form text to search Jira users by: display name, username, or email substring (e.g. ‘Smith’, ‘jane.doe’, ‘[e-mail]’). Server-side match is case-insensitive and partial.
project_key	string	No	Project key to scope the search to (e.g. ‘DT’). Required if issue_key is not given.
issue_key	string	No	Issue key to scope the search to (e.g. ‘DT-779’). Required if project_key is not given.
limit	integer	No	Maximum number of users to return (default 20).

---

Get Issue Watchers

Get the list of watchers for a Jira issue.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’)

---

Add Issue Watcher

Add a user as a watcher to a Jira issue.

This is a write tool. Disabled when READ_ONLY_MODE=true.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’)
user_identifier	string	Yes	User to add as watcher. For Jira Cloud, use the account ID. For Jira Server/DC, use the username.

---

Remove Issue Watcher

Remove a user from watching a Jira issue.

This is a write tool. Disabled when READ_ONLY_MODE=true.

Parameters:

Parameter	Type	Required	Description
issue_key	string	Yes	Jira issue key (e.g., ‘PROJ-123’)
username	string	No	Username to remove (for Jira Server/DC).
account_id	string	No	Account ID to remove (for Jira Cloud).

---