search_workitems
Search and filter work items by type, status, assignee, dates, and more to locate tasks, bugs, or requirements in Alibaba Cloud DevOps projects.
Instructions
[Project Management] Search work items with various filter conditions
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| organizationId | Yes | Organization ID | |
| category | Yes | Search for work item types, such as Req (requirement), Task (task), Bug (defect), etc., multiple values separated by commas | |
| spaceId | Yes | Project ID or Program ID. Use with spaceType to specify the space type | |
| spaceType | No | Space type: Project (project) or Program (project set). Default is Project. Use 'Program' when spaceId refers to a program (project set) ID | Project |
| subject | No | Text contained in the title | |
| status | No | Status ID, multiple separated by commas. Status names and their IDs: Pending Confirmation (28), Pending Processing (100005), Reopened (30), Deferred Fix (34), Confirmed (32), Selected (625489), In Analysis (154395), Analysis Complete (165115), In Progress (100010), In Design (156603), Design Complete (307012), In Development (142838), Development Complete (100011), In Testing (100012) | |
| createdAfter | No | Created not earlier than, format: YYYY-MM-DD | |
| createdBefore | No | Created not later than, format: YYYY-MM-DD | |
| updatedAfter | No | Updated not earlier than, format: YYYY-MM-DD | |
| updatedBefore | No | Updated not later than, format: YYYY-MM-DD | |
| creator | No | Creator user ID, multiple values separated by commas. Special value 'self' can be used to represent the current user | |
| assignedTo | No | Assignee user ID, multiple values separated by commas. Special value 'self' can be used to represent the current user | |
| sprint | No | Sprint ID, multiple values separated by commas | |
| workitemType | No | Work item type ID, multiple values separated by commas | |
| statusStage | No | Status stage ID, multiple values separated by commas | |
| tag | No | Tag ID, multiple values separated by commas | |
| priority | No | Priority ID, multiple values separated by commas | |
| subjectDescription | No | Text contained in title or description | |
| finishTimeAfter | No | Finish time not earlier than, format: YYYY-MM-DD | |
| finishTimeBefore | No | Finish time not later than, format: YYYY-MM-DD | |
| updateStatusAtAfter | No | Status update time not earlier than, format: YYYY-MM-DD | |
| updateStatusAtBefore | No | Status update time not later than, format: YYYY-MM-DD | |
| advancedConditions | No | Advanced filter conditions, JSON format | |
| orderBy | No | Sort field, default is gmtCreate. Possible values: gmtCreate, subject, status, priority, assignedTo | gmtCreate |
| sort | No | Sort order, default is desc. Possible values: desc (descending), asc (ascending) | desc |
| page | No | Page number, starting from 1. Default is 1 | |
| perPage | No | Number of items per page, range 0-200. Default is 20 | |
| includeDetails | No | Set to true when you need work item descriptions/detailed content. This automatically fetches missing descriptions instead of requiring separate get_work_item calls. RECOMMENDED: Use includeDetails=true when user asks for 'detailed content', 'descriptions', or 'full information' of work items. This is more efficient than calling get_work_item multiple times. Default is false |