Scheduling and timeline
Portfolio for Jira Home
On this page
In this section
Related content
- Send Notifications when pushing a commit that modifies files inside a specific folder
- Send Notifications when pushing a commit that modifies files inside a specific folder
- How to prevent creating branches with the prefixes that are not defined in the "Branching Model" using git hooks in Bitbucket Cloud?
- Syncing two repos in Pipelines error "unable to auto-detect email address"
- Bitbucket Cloud Pipelines Error: "[remote rejected] HEAD -> master (pre-receive hook declined)
- GIT commits from unknown users in Bitbucket Cloud
- Configure your DVCS username for commits
- Using repository hooks
- Configure your DVCS username for commits
- Map existing commits to username aliases
The schedule is one of core capabilities of Portfolio for Jira. The scheduling algorithm will automatically assign teams to issues, take dependencies and priorities into account, and generate a realistic forecast.
The timeline view shows forecasted release dates, and allows you to break things down based on projects, teams, and team members.
- Filter work by issue hierarchy
- See the forecasted schedule of work items: Use the visual timeframes at the top of the timeline to see when work items start and end
- Filter work by project, release, team, issue key, and issue summary
- Filter work by status category (To do, In progress, Done), specific status (Draft, In review, Validated), completion date, scheduled range, and theme
- Navigate to the scope view, teams view, and releases view: The view will display below the timeline of your plan
- Calculate the schedule of your plan: The calculation will be based on any changes made to work items in Portfolio for Jira or Jira
- View a plan's timeline, based on forecasted schedule of work, potential work capacity of the teams in the plan, or target schedules of the work items in the plan
- Generate read-only reports for a plan
- Configure the schedule view settings
To see the scheduling algorithm in action, check out some demo videos here.
Last modified on Sep 21, 2018
In this section
Related content
- Send Notifications when pushing a commit that modifies files inside a specific folder
- Send Notifications when pushing a commit that modifies files inside a specific folder
- How to prevent creating branches with the prefixes that are not defined in the "Branching Model" using git hooks in Bitbucket Cloud?
- Syncing two repos in Pipelines error "unable to auto-detect email address"
- Bitbucket Cloud Pipelines Error: "[remote rejected] HEAD -> master (pre-receive hook declined)
- GIT commits from unknown users in Bitbucket Cloud
- Configure your DVCS username for commits
- Using repository hooks
- Configure your DVCS username for commits
- Map existing commits to username aliases
Powered by Confluence and Scroll Viewport.