Top-level Planning Template

이 템플릿으로 다음을 만듭니다.

• A new issue level above the epic, called “initiative”

  • This allows you to group epics under an initiative and see underlying work nested within your plan.

• 새 프로젝트

  • The project is where the initiatives you create live.

• 새 계획

  • The plan is pre-configured with the new project as an issue source so you can see your initiatives in the plan. You can then add related projects, boards, and filters as issue sources and link underlying issues to the parent initiative.

To start, create your first initiative. Think of an initiative as a big chunk of work that multiple epics contribute to. For example, if your epics are things like “Build New functionality”, “Market new features”, and “Measure impact of release”, then your initiative might be something like “iOS Design Revamp”. Create one now; you can always add more later. Learn more about initiatives.

다음으로 이 계획에 기존 프로젝트, 보드 및/또는 필터를 추가하세요. 계획에서는 이것을 이슈 소스라고 합니다. 이 템플릿의 경우 회사에서 관리하는 프로젝트의 이슈를 사용하고 최소한 하나의 에픽을 포함하는 것이 좋습니다. 계획의 이슈 소스에 대해 자세히 알아보세요.

Finally, reparent your existing epics to the new initiatives. This creates an association using the Parent field, linking the two issues. You’ll see that the initiative now shows the data from the epics contained within. This is called a roll-up; the plan infer values of parents from child issues, and they’re useful for keeping your plan up to date. As you add more epics to the initiative, the estimates and dates will update along with it. Learn more about roll-ups in Plans.

Plans is a sandbox environment, meaning you need to save your changes before you’ll see them on any boards or projects outside your plan. Learn more about saving changes made in Plans.