Jira 工作流为高效的团队合作赋能
使用能够适应每个计划或项目的工作，规划、跟踪和发布出色的软件。从模板入手或创建自定义工作流，让团队更高效、更透明地开展工作。
提高透明度、问责制和工作效率
每个团队对于“完成”的定义及如何完成都有自己的看法。工作流是团队或组织内流程的直观表示。Jira 工作流由状态和转换组成，以便团队成员随时随地获得最准确的信息。
透明的项目管理
Jira 中的工作流可确保团队成员明确了解自己的任务，并可以查看其他所有人的工作量状态。通过使用工作流方案，工作流可以与特定项目和特定事务类型（可选）相关联。所有与项目相关的工作都会按状态进行组织（比如：待办、进行中、已完成等）
团队成员问责
将透明工作流管理扩展到支持团队和高管后，核心团队自然会感受到一种责任感。Jira 中健康的工作流可适应团队的需求。安排团队进行简短沟通，让团队成员能够发现所有障碍。
提高客户满意度
产品团队的一个常见痛点是估计某项功能何时才能完成并可供客户使用。通过按状态来组织工作，团队可以更准确地预测何时能完成某些功能并将其发布给用户。
总有工作流能助您一臂之力
Jira is designed for customizability because unique team goals and skill sets call for different Jira workflows. Here are a few ideas to get all of your company's teams started.
软件团队
Workflows in Jira help teams carry out their product vision. Track milestones and deliverables around the product roadmap, launches, bugs, sprint planning, and feedback. Learn more
业务和人力资源
Managing day-to-day operations requires efficient organization of numerous processes across teams. Track and manage new hire onboarding, candidates, internal resources, and company goals with customizable Jira workflows.
营销
Jira’s flexible workflows help non-technical teams track all milestones involved in Marketing campaign management—product launches, executing deliverables, and event planning.
而这还只是个开始。立即开始在 Jira 中构建工作流
项目管理
- 资产管理工作流
- 变更管理工作流
- 采购工作流
- 问题工作流
- 风险管理工作流
事务跟踪
- 帮助台工作流
- 缺陷跟踪工作流
- 事件工作流
- ITIL 工作流
- 工作单工作流
软件开发
- 代码审查工作流
- 发布管理工作流
- 需求管理
- 测试用例管理
- Devops 工作流
Jira 中引导工作流的敏捷方法
Scrum
Perhaps the most famous of the Agile methodologies, Scrum encourages team collaboration by focusing on a single goal at a time and delivering incrementally. A standard Scrum process begins with the creation of a product backlog, which in simple terms, is really the team's to-do list. Each team member plans how much of the backlog he or she can complete in a given timeframe (the "Sprint," typically two weeks). The Sprint begins and team builds the product. At the end of each Sprint, the team determines what work to tackle next based on the outcome of the previous Sprint. And the process repeats. Learn scrum with Jira
看板
Unlike Scrum, Kanban focuses on status rather than due dates. Each item of work progresses through pre-defined project stages so teams can easily see what work is in-progress and identify roadblocks. A basic kanban board is a three-step workflow: To Do, In Progress, and Done. But depending on the unique requirements and composition of your team, additional workflow stages can be mapped in. Learn kanban with Jira
混合方法
Agile teams often adopt mixed methodologies and that's where Jira's customizability becomes so powerful. For example, scrumban takes fixed-length sprints and roles from scrum and the focus on WIP (work in progress) limits and cycle time from kanban. Or kanplan, which is kanban with a backlog.
Jira 长篇故事和故事
While not a methodology per se, epics and stories are Agile artifacts to classify amount of work and are a significant part of how teams manage work in Jira. An epic captures a large body of work that can be broken down into a number of smaller tasks. Those smaller tasks, called user stories, are an effective way to write product backlog items. When utilized, they are often written from the point of view of end-users. Learn how to use epics in Jira
不确定哪种敏捷方法适合您？了解有关敏捷项目管理的更多信息。
Best practices for workflows in Jira
让每个人都保持一致：花点时间了解团队和利益相关者的关切点，以争取获得他们的支持并确保一致。
反映工作流实际情况：设计 Jira 工作流以与业务流程保持一致，然后根据工作流/事务类型结构决定最适合的工作流。
保持工作流的简易性：使工作流保持简单。包含对报告和可见性至关重要的状态。
根据需要细化和优化工作流：允许在合理范围内进行路线修正，以在不影响报告的情况下实现一定的灵活性。
不断向前推进工作：确保所有事务都有指向其他状态的路径，以便您的团队可以继续向前推进工作。
Using Jira to manage workflows
Simple workflow building blocks in Jira allows organizations to start simple and customize as they grow.
状态显示某项工作在工作流中所处的阶段。经办人是某项工作的责任方。
转换是状态之间的链接，允许工作从一种状态转为另一种状态。
决议解释了某项工作被关闭的原因，原因包括被取消、已解决或者已上报。
通过 Jira Automation 来连接整个工作流
使用 Automation 将您的第三方工具无缝连接到任何 Jira 工作流。无论您的团队使用的是 Bitbucket、Slack 还是任何其他工具，Automation 都能使 Jira 保持最新状态，因此不必您进行更新。了解更多