Skip to content

Commit f707f3e

Browse files
committed
fixup! jira
wip
1 parent 00a08d6 commit f707f3e

16 files changed

+269
-143
lines changed

examples/jira/config.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,8 @@ projects:
88
profiles:
99
default:
1010
secrets:
11-
# JIRA credentials - using "python" type to see DuckDB injection failure
1211
- name: "jira"
13-
type: "python" # This will cause DuckDB injection to fail
12+
type: "python"
1413
parameters:
1514
url: "https://your-domain.atlassian.net"
1615
username: "your-email@example.com"

examples/jira/tools/get_issue.yml

Lines changed: 35 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ tool:
44
name: get_issue
55
description: |
66
Get detailed information for a specific JIRA issue by its key.
7-
Returns comprehensive issue data including status, assignee, description, and metadata.
7+
Returns comprehensive issue information including all fields, assignee, reporter, etc.
88
type: tool
99
annotations:
10-
title: Get Issue Details
10+
title: Get Issue
1111
readOnlyHint: true
1212
destructiveHint: false
1313
idempotentHint: true
@@ -19,100 +19,99 @@ tool:
1919
- name: issue_key
2020
type: string
2121
description: |
22-
The JIRA issue key to retrieve. This is the unique identifier for the issue
23-
(e.g., 'RD-123', 'TEST-456', 'PROJ-789').
24-
Issue keys are typically in the format: PROJECT_KEY-NUMBER.
22+
The issue key (e.g., 'RD-123', 'TEST-456').
23+
This is the unique identifier for the issue visible in the Jira UI.
2524
examples: [
2625
"RD-123",
27-
"TEST-456",
28-
"PROJ-789",
29-
"DEV-42"
26+
"TEST-456",
27+
"PROJ-789"
3028
]
3129
return:
3230
type: object
3331
properties:
3432
key:
3533
type: string
36-
description: The issue key (e.g., "RD-123")
34+
description: The issue key
3735
id:
3836
type: string
39-
description: Internal numeric ID of the issue
37+
description: The issue ID
4038
summary:
4139
type: string
42-
description: Issue title/summary
40+
description: The issue summary
4341
description:
4442
type: string
45-
description: Detailed description of the issue
43+
description: The issue description
4644
status:
4745
type: string
48-
description: Current status (e.g., "To Do", "In Progress", "Done")
46+
description: The current status
4947
assignee:
5048
type: string
51-
description: Display name of the person assigned to this issue
49+
description: The assignee display name
5250
assignee_account_id:
5351
type: string
54-
description: Account ID of the assignee
52+
description: The assignee account ID
5553
reporter:
5654
type: string
57-
description: Display name of the person who reported this issue
55+
description: The reporter display name
5856
reporter_account_id:
5957
type: string
60-
description: Account ID of the reporter
58+
description: The reporter account ID
6159
issue_type:
6260
type: string
63-
description: Type of issue (e.g., "Bug", "Story", "Task", "Epic")
61+
description: The issue type
6462
priority:
6563
type: string
66-
description: Priority level (e.g., "High", "Medium", "Low")
64+
description: The priority level
6765
resolution:
6866
type: string
69-
description: Resolution status if resolved (e.g., "Fixed", "Won't Fix")
67+
description: The resolution
7068
resolution_date:
7169
type: string
72-
description: Date when the issue was resolved (ISO format)
70+
description: The resolution date
7371
created:
7472
type: string
75-
description: Date when the issue was created (ISO format)
73+
description: The creation date
7674
updated:
7775
type: string
78-
description: Date when the issue was last updated (ISO format)
76+
description: The last update date
7977
due_date:
8078
type: string
81-
description: Due date for the issue (ISO format)
79+
description: The due date
8280
labels:
8381
type: array
8482
items:
8583
type: string
86-
description: Labels/tags associated with the issue
84+
description: The issue labels
8785
components:
8886
type: array
8987
items:
9088
type: string
91-
description: Components this issue belongs to
89+
description: The issue components
9290
fix_versions:
9391
type: array
9492
items:
9593
type: string
96-
description: Versions where this issue will be/was fixed
94+
description: The fix versions
9795
project:
9896
type: object
9997
properties:
10098
key:
10199
type: string
102-
description: Project key (e.g., "RD")
103100
name:
104101
type: string
105-
description: Project name
106-
description: Project information
102+
description: The project information
107103
parent:
108104
type: string
109-
description: Parent issue key if this is a subtask
105+
description: The parent issue key
110106
url:
111107
type: string
112-
description: Direct URL to view the issue in JIRA web UI
108+
description: The issue URL
113109
self:
114110
type: string
115-
description: REST API URL for this issue resource
116-
description: |
117-
Comprehensive issue information including all key fields, metadata, and relationships.
118-
Raises an error if the issue key is invalid or not accessible.
111+
description: The API self link
112+
tests:
113+
- name: "Get issue by key"
114+
description: "Verify issue retrieval returns expected structure"
115+
arguments:
116+
- key: issue_key
117+
value: "RD-15333"

examples/jira/tools/get_project.yml

Lines changed: 51 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ mxcp: 1
33
tool:
44
name: get_project
55
description: |
6-
Get details for a specific project in your Jira instance by its project key.
7-
Returns comprehensive project information including configuration and metadata.
6+
Get details for a specific project by its key.
7+
Returns comprehensive project information including description, settings, and lead.
88
type: tool
99
annotations:
10-
title: Get Project Details
10+
title: Get Project
1111
readOnlyHint: true
1212
destructiveHint: false
1313
idempotentHint: true
@@ -19,15 +19,58 @@ tool:
1919
- name: project_key
2020
type: string
2121
description: |
22-
The project key to search for. This is the short identifier for the project (e.g., 'TEST' for project TEST).
23-
Project keys are typically uppercase and contain only letters and numbers.
22+
The project key (e.g., 'TEST' for project TEST).
23+
This is the short identifier for the project.
2424
examples: [
2525
"TEST",
2626
"PROJ",
2727
"DEV"
2828
]
2929
return:
3030
type: object
31-
description: |
32-
Project details object containing comprehensive information about the Jira project.
33-
Raises an error if project is not found or access is denied.
31+
properties:
32+
key:
33+
type: string
34+
description: The project key
35+
name:
36+
type: string
37+
description: The project name
38+
description:
39+
type: string
40+
description: The project description
41+
projectTypeKey:
42+
type: string
43+
description: The project type key
44+
simplified:
45+
type: boolean
46+
description: Whether the project is simplified
47+
style:
48+
type: string
49+
description: The project style
50+
isPrivate:
51+
type: boolean
52+
description: Whether the project is private
53+
archived:
54+
type: boolean
55+
description: Whether the project is archived
56+
lead:
57+
type: object
58+
properties:
59+
displayName:
60+
type: string
61+
emailAddress:
62+
type: string
63+
accountId:
64+
type: string
65+
active:
66+
type: boolean
67+
description: The project lead information
68+
url:
69+
type: string
70+
description: The project URL
71+
tests:
72+
- name: "Get project by key"
73+
description: "Verify project retrieval returns expected structure"
74+
arguments:
75+
- key: project_key
76+
value: "RD"

examples/jira/tools/get_project_role_users.yml

Lines changed: 19 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ mxcp: 1
33
tool:
44
name: get_project_role_users
55
description: |
6-
Get users and groups assigned to a specific role in a JIRA project.
7-
Returns detailed information about users and groups for the specified role.
6+
Get users and groups for a specific role in a project.
7+
Returns detailed information about users and groups assigned to the role.
88
type: tool
99
annotations:
1010
title: Get Project Role Users
@@ -19,8 +19,8 @@ tool:
1919
- name: project_key
2020
type: string
2121
description: |
22-
The project key to get role users for. This is the short identifier for the project (e.g., 'TEST' for project TEST).
23-
Project keys are typically uppercase and contain only letters and numbers.
22+
The project key (e.g., 'TEST' for project TEST).
23+
This is the short identifier for the project.
2424
examples: [
2525
"TEST",
2626
"PROJ",
@@ -29,13 +29,12 @@ tool:
2929
- name: role_name
3030
type: string
3131
description: |
32-
The name of the role to get users for. This should be an exact match for one of the roles in the project.
33-
Use get_project_roles to see available roles.
32+
The name of the role to get users for.
33+
Common roles include 'Administrators', 'Developers', 'Users'.
3434
examples: [
3535
"Administrators",
36-
"Developers",
37-
"Service Desk Team",
38-
"CI"
36+
"Developers",
37+
"Users"
3938
]
4039
return:
4140
type: object
@@ -48,37 +47,32 @@ tool:
4847
description: The role name
4948
role_id:
5049
type: string
51-
description: The unique role ID
50+
description: The role ID
5251
users:
5352
type: array
5453
items:
5554
type: object
5655
properties:
5756
accountId:
5857
type: string
59-
description: Unique account identifier for the user
6058
displayName:
6159
type: string
62-
description: Display name of the user
63-
emailAddress:
64-
type: string
65-
description: Email address of the user
66-
active:
67-
type: boolean
68-
description: Whether the user account is active
69-
description: List of users assigned to this role
60+
description: List of users in the role
7061
groups:
7162
type: array
7263
items:
7364
type: object
7465
properties:
7566
name:
7667
type: string
77-
description: Name of the group
7868
groupId:
7969
type: string
80-
description: Unique group identifier
81-
description: List of groups assigned to this role
82-
description: |
83-
Users and groups assigned to the specified role in the project.
84-
Raises an error if project or role is not found, or access is denied.
70+
description: List of groups in the role
71+
tests:
72+
- name: "Get role users"
73+
description: "Verify role users returns expected structure"
74+
arguments:
75+
- key: project_key
76+
value: "RD"
77+
- key: role_name
78+
value: "Administrators"

examples/jira/tools/get_project_roles.yml

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ mxcp: 1
33
tool:
44
name: get_project_roles
55
description: |
6-
Get all roles available in a JIRA project.
7-
Returns a list of roles with their names, IDs, and URLs.
6+
Get all roles available in a project.
7+
Returns a list of roles with their IDs and URLs.
88
type: tool
99
annotations:
1010
title: Get Project Roles
@@ -19,8 +19,8 @@ tool:
1919
- name: project_key
2020
type: string
2121
description: |
22-
The project key to get roles for. This is the short identifier for the project (e.g., 'TEST' for project TEST).
23-
Project keys are typically uppercase and contain only letters and numbers.
22+
The project key (e.g., 'TEST' for project TEST).
23+
This is the short identifier for the project.
2424
examples: [
2525
"TEST",
2626
"PROJ",
@@ -33,13 +33,16 @@ tool:
3333
properties:
3434
name:
3535
type: string
36-
description: The name of the role (e.g., "Administrators", "Developers")
36+
description: The role name
3737
id:
3838
type: string
39-
description: The unique ID of the role
39+
description: The role ID
4040
url:
4141
type: string
42-
description: The REST API URL for this role
43-
description: |
44-
List of roles available in the project. Each role contains name, ID, and URL information.
45-
Raises an error if project is not found or access is denied.
42+
description: The role URL
43+
tests:
44+
- name: "Get project roles"
45+
description: "Verify project roles returns array of roles"
46+
arguments:
47+
- key: project_key
48+
value: "RD"

0 commit comments

Comments
 (0)