Zadig 文档
Zadig
教程
博客
论坛
关于
中文英文
Zadig
教程
博客
论坛
关于
Zadig v3.4
Loading...
     编辑文档
     反馈问题
     社区讨论

    本页导航

    Release Plan

    This article primarily explains how to use Zadig's release plan feature, including planning, approval, and execution of release plans, as well as tracking detailed operation records.

    # Planning

    Access Management -> Release Plan: Create a new release plan, fill in the details, and save it as a draft. This feature supports multi-person collaboration for planning the release.

    Release Plan

    Parameter Description:

    • Name: The name of the release plan
    • Release Owner: The person responsible for this release. After the release plan is formulated, only the owner can execute the release
    • Release Window: The time window during which publishing operations can be performed
    • Scheduled Execution: Execute the workflow in the release items at a specified time
    • Requirement Association: The associated requirement list, supporting multiple JIRA sprints
    • Release Content: Specific release content, which can include two types: rich text and workflow
      • Rich Text Type: Input content
      • Workflow Type: Select the project and workflow in Zadig and configure the workflow parameters as needed
    • Approval Configuration: Configure approval as needed, supporting three methods: Zadig, Feishu, and DingTalk
      • Zadig : The approval application will be sent to the email address corresponding to the account Zadig For specific approval configuration, please refer to the document Zadig
      • Feishu : The approval application will be sent to Feishu. For specific approval configuration, please refer to the document Feishu for approval.
      • Dingtalk : The approval application will be sent to DingTalk. For specific approval configuration, please refer to the document DingTalk approval.

    # Approval

    This applies to scenarios where the release plan includes approval configuration.

    After the release owner submits the approval, the approver is responsible for the approval. Only after the approval is granted can the release owner proceed with the release.

    Tip

    If the approval is rejected, the release plan content can be edited again and the release plan can be re-planned.

    Release Plan

    # Execution

    Tip

    1. Execution can be performed within the release time window.
    2. Only the release owner can execute the release.

    For rich text type release content, click Complete on the right and enter the release notes.

    Release Plan

    For workflow type release content, click Execute on the right to automatically trigger the workflow execution. Click the link to view the workflow execution details.

    For release items that need to be skipped, click Skip. Once all release items are either executed or skipped, the release plan will be automatically marked as completed.

    # Operation Record

    The system keeps a detailed record of the release plan's operation logs. Click Operation Record to view them.

    Release Plan

    ← Release Process PracticeOverview→

    资源
    教程
    论坛
    博客
    公司
    关于
    客户故事
    加入我们
    联系我们
    微信扫一扫
    hello@koderover.com

    © 2026 筑栈(上海)信息技术有限公司 沪 ICP 备 19000177 号 - 1

    •  跟随系统
    •  浅色模式
    •  深色模式
    •  阅读模式