Scope
Portfolio for Jira Home
- Discovering Portfolio for Jira
- Getting started
- Administering plans
- Overview
- Setting up the planning environment
- What is a plan
- Working with Portfolio plans
- Managing teams and releases
- Saving changes in Jira
- Sharing and exporting plan data
- Live plans (versions 2.0 to 2.27)
- Live plans
- Programs
- Scope
- Scheduling and timeline
- Teams
- Releases
- Reports
- Portfolio for Jira Server GDPR support guides
On this page
In this section
Related content
- No related content found
This page discusses the usage of Portfolio for Jira live plans. If you're using the redesigned planning interface, see this page instead.
Plans feature a seamless integration with Jira. Changes that happen in the selected agile boards and projects will be reflected in your plan in Portfolio for Jira. It also works the other way around; the new "review changes" dialog provides you with a full view of changes that have been made before committing them back to Jira.
In addition, you can create and customize unlimited hierarchical levels. The scope is usually composed of three key hierarchical levels by default:
- Epics - Once higher-level priorities are settled, it's necessary to break them down into large pieces of work, which consist of multiple stories.
- Stories - These are the user stories capture functionality requirements.
- Sub-task - These are the work components that make up stories.
Last modified on Apr 5, 2020
In this section
Related content
- No related content found
Powered by Confluence and Scroll Viewport.