pub trait SubTaskApi {
// Required methods
fn create_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
request: CreateSubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<i64>> + Send;
fn update_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
node_id: &str,
task_id: i64,
request: UpdateSubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<()>> + Send;
fn delete_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
task_id: i64,
auth: AuthType,
) -> impl Future<Output = ApiResult<()>> + Send;
fn modify_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
request: ModifySubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<()>> + Send;
fn get_subtasks(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
node_id: Option<&str>,
auth: AuthType,
) -> impl Future<Output = ApiResult<GetSubTaskResponse>> + Send;
fn search_subtasks(
&self,
request: SearchSubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<SearchSubTaskResponse>> + Send;
}Required Methods§
Sourcefn create_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
request: CreateSubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<i64>> + Send
fn create_subtask( &self, project_key: &str, work_item_type_key: &str, work_item_id: i64, request: CreateSubTaskRequest, auth: AuthType, ) -> impl Future<Output = ApiResult<i64>> + Send
创建子任务 该接口用于在一个工作项实例的指定节点上创建一个子任务,对应平台的功能可参考新增任务。 对应的权限申请在权限管理-子任务分类下,相关功能介绍详见权限管理。
Sourcefn update_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
node_id: &str,
task_id: i64,
request: UpdateSubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<()>> + Send
fn update_subtask( &self, project_key: &str, work_item_type_key: &str, work_item_id: i64, node_id: &str, task_id: i64, request: UpdateSubTaskRequest, auth: AuthType, ) -> impl Future<Output = ApiResult<()>> + Send
更新子任务 该接口用于更新工作项实例指定节点上的一个子任务详细信息,对应平台的功能, 如实例侧操作可参考任务管理,如流程节点上默认的子任务配置可参考完成任务。
Sourcefn delete_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
task_id: i64,
auth: AuthType,
) -> impl Future<Output = ApiResult<()>> + Send
fn delete_subtask( &self, project_key: &str, work_item_type_key: &str, work_item_id: i64, task_id: i64, auth: AuthType, ) -> impl Future<Output = ApiResult<()>> + Send
删除子任务 该接口用于删除指定工作项实例中的一个子任务,对应平台的功能可参考任务管理。 对应的权限申请在权限管理-子任务分类下,相关功能介绍详见权限管理。
Sourcefn modify_subtask(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
request: ModifySubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<()>> + Send
fn modify_subtask( &self, project_key: &str, work_item_type_key: &str, work_item_id: i64, request: ModifySubTaskRequest, auth: AuthType, ) -> impl Future<Output = ApiResult<()>> + Send
子任务完成/回滚 该接口用于完成或者回滚工作项实例指定节点上的一个子任务,对应平台的功能, 如实例侧操作可参考任务管理,如流程节点上默认的子任务配置可参考完成任务。 对应的权限申请在权限管理-子任务分类下,相关功能介绍详见权限管理。
Sourcefn get_subtasks(
&self,
project_key: &str,
work_item_type_key: &str,
work_item_id: i64,
node_id: Option<&str>,
auth: AuthType,
) -> impl Future<Output = ApiResult<GetSubTaskResponse>> + Send
fn get_subtasks( &self, project_key: &str, work_item_type_key: &str, work_item_id: i64, node_id: Option<&str>, auth: AuthType, ) -> impl Future<Output = ApiResult<GetSubTaskResponse>> + Send
获取指定工作项实例上的子任务详细信息 该接口用于获取指定工作项实例上的子任务详细信息,对应平台的功能, 如实例侧操作可参考任务管理,如流程节点上默认的子任务配置可参考完成任务。 对应的权限申请在权限管理-子任务分类下,相关功能介绍详见权限管理。
Sourcefn search_subtasks(
&self,
request: SearchSubTaskRequest,
auth: AuthType,
) -> impl Future<Output = ApiResult<SearchSubTaskResponse>> + Send
fn search_subtasks( &self, request: SearchSubTaskRequest, auth: AuthType, ) -> impl Future<Output = ApiResult<SearchSubTaskResponse>> + Send
获取指定的子任务列表(跨空间) 该接口用于跨空间搜索符合传入条件的子任务,对应平台的功能, 如实例侧操作可参考任务管理,如流程节点上默认的子任务配置可参考完成任务。 对应的权限申请在权限管理-子任务分类下,相关功能介绍详见权限管理。
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.