vansah_add_test_case_step
ChatGPTAdd a manual action/expected-result step to an existing Vansah test case version in an authorized Vansah-enabled project. This is a state-changing operation; a retry can add a duplicate step, so retry only after confirming the first request did not complete.
vansah_create_advanced_plan_test_runs
ChatGPTRecord execution results for selected cases under a specific requirement in an advanced Vansah test plan. Accepts a full testPlanKey, a stable identifier, or a plan name. Returns each saved run's UUID, numeric runKey and full testRunKey when supplied by the backend. This is a state-changing operation; a retry can record duplicate execution results, so retry only after confirming the first request did not complete.
vansah_create_advanced_test_plan
ChatGPTCreate an advanced Vansah test plan across one or more Jira issue requirements and/or test folders in an authorized project. This is a state-changing operation; a retry can create a duplicate advanced plan.
vansah_create_folder_test_runs
ChatGPTCreate Vansah test run results for one or more test cases under a Vansah test folder. This is a state-changing operation; a retry can record duplicate execution results, so retry only after confirming the first request did not complete.
vansah_create_issue_test_runs
ChatGPTCreate Vansah test run results for one or more test cases against a Jira issue asset in an authorized project. This is a state-changing operation; a retry can record duplicate execution results, so retry only after confirming the first request did not complete.
vansah_create_test_case
ChatGPTCreate a single Vansah test case in an authorized Vansah-enabled project, optionally with an initial manual, plain-text, or BDD script and script attachments. This is a state-changing operation; a retry can create a duplicate test case, so retry only when the first request did not complete. Attachments may use legacy Base64, trusted URLs, or batch attachment tokens from vansah_prepare_attachment_uploads. Workflow: call vansah_list_projects first, then pass a returned projectKey; call vansah_list_project_metadata for caseTypes; call vansah_list_folders when placing the case in a folder.
vansah_create_test_case_version
ChatGPTCreate a new version of an existing Vansah test case, copying from a source version. This is a state-changing operation; a retry can create another version. Defaults to the case's current version when sourceVersionNumber is omitted.
vansah_create_test_folder
ChatGPTCreate a Vansah test folder in an authorized Vansah-enabled project. This is a state-changing operation; a retry can create a duplicate folder, so retry only when the first request did not complete. Workflow: call vansah_list_projects first, then pass a returned projectKey; call vansah_list_folders when creating under a parent folder.
vansah_create_test_plan
ChatGPTCreate a standard Vansah planned test run/test plan in an authorized project. This is a state-changing operation; a retry can create a duplicate plan. Requires exactly one target: issueKey or a test folder identifier/name/path, plus startDate and endDate. Optionally place it in a test plan folder.
vansah_create_test_plan_runs
ChatGPTRecord execution results for selected cases in a standard Vansah test plan iteration. Accepts a full testPlanKey such as KAN-P47, a stable identifier, or a plan name. Returns each saved run's UUID, numeric runKey and full testRunKey when supplied by the backend. This is a state-changing operation; a retry can record duplicate execution results, so retry only after confirming the first request did not complete.
vansah_get_burnup_report
ChatGPTGet a Vansah burnup trend report for a project. Workflow: call vansah_list_projects first, then pass projectKey. Optional scope filters can use issueKeys, folderIdentifiers/folderNames/folderPaths, or testPlanIdentifiers/testPlanNames. customiseDays must be EVERY_DAY or EXCLUDE_WEEKENDS.
vansah_get_coverage_report
ChatGPTGet a Vansah coverage/Test Summary Report for a project scope. Workflow: call vansah_list_projects first, then pass projectKey and at least one scope: issueKeys, folderIdentifiers/folderNames/folderPaths, or testPlanIdentifiers/testPlanNames. Prefer identifiers from vansah_list_folders over guessed names.
vansah_get_jira_board_work_items
ChatGPTRead board work items only within the Jira site selected by the authenticated MCP session (or its first authorized site when no selection exists), using that user's Jira permissions. Prefer boardId when known; otherwise provide projectKey and an unambiguous boardName. Optional issueTypes/statuses narrow the board issue query. This is a read-only lookup in a bounded account/workspace: board IDs and names cannot select another site or an arbitrary URL, and no Jira data is created, changed, or deleted.
vansah_get_project
ChatGPTGet one Vansah project by key or ID. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools.
vansah_get_test_case
ChatGPTGet one test case by canonical caseKey from vansah_search_test_cases (for example SCRUM-C1). Do not construct case keys from numeric IDs. Returns caseKey, publicKey, and any linked issues. Pass includeScripts to also return script content; manual step scripts include attachment URL metadata when available.
vansah_get_test_case_history
ChatGPTGet the change/audit history of a test case (who changed what and when). Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Pass caseKey from vansah_search_test_cases (e.g. SCRUM-C1).
vansah_get_test_execution_report
ChatGPTGet an aggregated Vansah Test Execution Report for a project. Workflow: call vansah_list_projects first, then pass projectKey. startDate and endDate are required in YYYY-MM-DD format. Optional scope filters can use issueKeys, folderIdentifiers/folderNames/folderPaths, or testPlanIdentifiers/testPlanNames. groupBy must be one of date, label, issue, component, assigned_to, or priority.
vansah_get_test_plan
ChatGPTRetrieve full details for one Vansah planned test run/test plan by stable identifier, test-plan key, or by an unambiguous name within an authorized project. Advanced requirement assets retain their assetType and folder/issue UUID, name, and path; those assets do not receive a testPlanKey. Workflow: call vansah_list_projects first; use vansah_list_test_plan_folders or a list/search result to avoid ambiguous names.
vansah_get_test_run
ChatGPTGet one test run. projectKey is always required, plus either sequenceKey or runId.
vansah_get_test_run_logs
ChatGPTGet the per-step execution results of a test run (each step's actual result, status, and comments). Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. projectKey is always required, plus sequenceKey or runId from vansah_list_test_runs.
vansah_get_test_scripts
ChatGPTGet test script content for a test case (steps, plain text, or BDD). Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Pass canonical caseKey from vansah_search_test_cases (e.g. SCRUM-C1); do not construct case keys from numeric IDs. Omit type to auto-detect from the case script type. Manual step scripts include attachment URL metadata when available.
vansah_import_test_cases
ChatGPTImport multiple Vansah test cases into an authorized Vansah-enabled project in one batch. This is a state-changing operation; a retry can import duplicates, so confirm the first batch did not complete before retrying. Workflow: call vansah_list_projects first, then pass a returned projectKey; call vansah_list_project_metadata for caseTypes; call vansah_list_folders when placing cases in folders.
vansah_link_test_cases_to_container
ChatGPTLink existing Vansah test cases to exactly one test folder or test plan in an authorized project. Test plans accept a stable UUID, canonical key such as KAN-P65, or an unambiguous name. This is a state-changing operation; a retry can repeat the link request, so retry only after confirming the first request did not complete. Workflow: call vansah_list_projects first, use vansah_search_test_cases for case keys/identifiers, and use vansah_list_folders with includePlannedRuns or vansah_list_test_plans when resolving folders or plans.
vansah_link_test_cases_to_issue
ChatGPTLink one or more existing Vansah test cases to a Jira issue in an authorized Vansah-enabled project. This is a state-changing operation; a retry can repeat the link request, so retry only after confirming the first request did not complete. Workflow: call vansah_list_projects first, then pass a returned projectKey; call vansah_search_test_cases first if case keys or identifiers are unknown.
vansah_list_folders
ChatGPTList test folders and issue folders. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Folder paths are resolved against the complete flat folder index before the display limit is applied. When includePlannedRuns is true, plannedRuns and canonical testPlanKeys are returned separately for vansah_list_test_plan_test_cases.
vansah_list_jira_components
ChatGPTRead Jira components only within the Jira site selected by the authenticated MCP session (or its first authorized site when no selection exists), using that user's Jira permissions. Requires projectKey; optional name filters and pagination select components within that site. This is a read-only lookup in a bounded account/workspace: inputs cannot select another site or an arbitrary URL, and no Jira data is created, changed, or deleted.
vansah_list_linked_issues
ChatGPTList Jira issues linked to a test case. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Pass caseKey from vansah_search_test_cases (e.g. SCRUM-C1). Empty linkedIssues means the case exists but has no linked issues.
vansah_list_project_metadata
ChatGPTReturn lookup tables for a project: statuses, priorities, case types, environments, releases, and sprints. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Use the returned IDs with vansah_search_test_cases filters.
vansah_list_projects
ChatGPTList Vansah-enabled project spaces for the user. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Do not use Jira-only spaces that are not in this list.
vansah_list_test_case_test_plans
ChatGPTList the test plans a test case belongs to. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Pass caseKey from vansah_search_test_cases (e.g. SCRUM-C1).
vansah_list_test_case_versions
ChatGPTList the versions of a test case (version number, default flag, script type). Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Use the versionNumber with vansah_get_test_scripts to read a specific version.
vansah_list_test_plan_folders
ChatGPTList the test plan folders of a project. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Pass folderPath to resolve a named test plan folder and return its direct child folders and plans linked through the test-plan-folder association, including canonical testPlanKeys. Upstream lookup failures are returned as errors.
vansah_list_test_plan_test_cases
ChatGPTList test cases linked to a test plan or planned run. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. Call vansah_list_folders with includePlannedRuns: true first to get a real testPlanKey (e.g. SCRUM-P1). Do not invent plan keys.
vansah_list_test_plans
ChatGPTList planned Vansah test plans in a project with optional name, folder, type, status, date, sort, and pagination filters. Workflow: call vansah_list_projects first, then pass projectKey.
vansah_list_test_results
ChatGPTList test result values for a workspace. Use defaultName, not the editable display name, when calling MCP Test Run create or update tools.
vansah_list_test_run_linked_issues
ChatGPTList Jira issues and defects linked to a test run. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. projectKey is always required, plus sequenceKey or runId from vansah_list_test_runs.
vansah_list_test_runs
ChatGPTList test runs in a project, optionally filtered by test case or result. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. An empty list means the project has no executed runs yet.
vansah_prepare_attachment_uploads
ChatGPTPrepare up to 200 direct S3 uploads for a complete test-case script, with a maximum of 100 MiB per file and 500 MiB aggregate metadata batch size. This is a state-changing preparation operation that creates temporary upload intents; a retry can create another batch, so use one returned batch for the final write. Pass metadata only; do not pass Base64 content. Use the returned attachment tokens in one final vansah_create_test_case or vansah_update_test_case call. Base64 attachments remain supported directly by those final tools and do not need preparation.
vansah_search_jira_work_items
ChatGPTRead Jira work items only within the Jira site selected by the authenticated MCP session (or its first authorized site when no selection exists), using that user's Jira permissions. Provide explicit jql, or filters such as projectKey, searchText, issueTypes, and statuses. JQL selects data within that site; it does not select another site or an arbitrary URL. This is a read-only search in a bounded account/workspace and does not create, change, or delete Jira data.
vansah_search_test_cases
ChatGPTSearch test cases in a project by text, status, priority, or type. Workflow: call vansah_list_projects first, then pass projectKey on project-scoped tools. You can pass names such as priorityName: "High" and typeName: "Functional"; MCP resolves metadata when available and uses Vansah backend name filters when supported.
vansah_update_test_case
ChatGPTUpdate editable fields and optionally replace the full manual, plain-text, BDD, or automation script on an existing Vansah test case. This is a destructive state-changing operation: supplied fields overwrite existing values and supplied script content replaces the complete script; a retry repeats that replacement. Script replacements can include legacy Base64/URL attachments, existing attachment IDs, or batch attachment tokens from vansah_prepare_attachment_uploads. Workflow: call vansah_list_projects first, use vansah_search_test_cases to find the case, and call vansah_list_project_metadata or vansah_list_folders before using friendly metadata or folder names.
vansah_update_test_case_script
ChatGPTReplace the BDD or plain-text script content for an existing Vansah test case version. This is a destructive state-changing operation: it creates the script if the selected version does not already have one, otherwise it replaces the existing script content; a retry repeats the full replacement.
vansah_update_test_case_step
ChatGPTUpdate action, expected result, test data, or position for an existing manual Vansah test case step. This is a destructive state-changing operation: supplied values overwrite the existing step and a retry repeats that overwrite; no reliable user undo is exposed.
vansah_update_test_run
ChatGPTUpdate the overall result and optionally record an actual result for an existing Vansah test run by numeric key, full key such as KAN-R334, or stable UUID identifier. The backend stores actualResult as a test run comment for multistep scripts and as the first execution step's actual result for other script types. A full key supplies its own project scope; numeric keys and UUIDs require projectKey. This is a destructive state-changing operation: it overwrites execution data and a retry repeats that change. Call vansah_list_test_results first and pass the result's defaultName.
vansah_whoami
ChatGPTShow the Atlassian account and Vansah region/data residency details for this MCP session.
vansah_add_test_case_step
Claudevansah_create_advanced_plan_test_runs
Claudevansah_create_advanced_test_plan
Claudevansah_create_folder_test_runs
Claudevansah_create_issue_test_runs
Claudevansah_create_test_case
Claudevansah_create_test_case_version
Claudevansah_create_test_folder
Claudevansah_create_test_plan
Claudevansah_create_test_plan_runs
Claudevansah_get_burnup_report
Claudevansah_get_coverage_report
Claudevansah_get_jira_board_work_items
Claudevansah_get_project
Claudevansah_get_test_case
Claudevansah_get_test_case_history
Claudevansah_get_test_execution_report
Claudevansah_get_test_plan
Claudevansah_get_test_run
Claudevansah_get_test_run_logs
Claudevansah_get_test_scripts
Claudevansah_import_test_cases
Claudevansah_link_test_cases_to_container
Claudevansah_link_test_cases_to_issue
Claudevansah_list_folders
Claudevansah_list_jira_components
Claudevansah_list_linked_issues
Claudevansah_list_project_metadata
Claudevansah_list_projects
Claudevansah_list_test_case_test_plans
Claudevansah_list_test_case_versions
Claudevansah_list_test_plan_folders
Claudevansah_list_test_plan_test_cases
Claudevansah_list_test_plans
Claudevansah_list_test_results
Claudevansah_list_test_run_linked_issues
Claudevansah_list_test_runs
Claudevansah_prepare_attachment_uploads
Claudevansah_search_jira_work_items
Claudevansah_search_test_cases
Claudevansah_update_test_case
Claudevansah_update_test_case_script
Claudevansah_update_test_case_step
Claudevansah_update_test_run
Claudevansah_whoami
Claude