Plan
Portfolio for Jira Home
On this page
In this section
Related content
- How to figure out if a branch was deleted on merge in Bitbucket Server
- Repository notifications
- Using repository hooks
- View and configure the audit log
- Commit history
- How to identify a deleted branch
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- Missing Commits in Bitbucket Server
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- Compare branches, tags, and commits
A plan contains your issues, teams, and releases, and allows you to calculate the schedule of your projects. You can create any number of plans, which can be accessed by different users and groups.
Plans can change over time for several reasons – you may gain more knowledge, so you can therefore refine remaining estimates more accurately, or project requirements have become clearer, or tasks have been completed faster than expected. Portfolio for Jira helps you keep your plans up-to-date by syncing these with the activities that actually happened from day to day.
Having a clear, achievable schedule gives your team transparency on how things are going. Knowing what's next helps your team make better day-to-day decisions, even if plans change frequently. The following sections contain information on how to create and manage plans.
In this section
Related content
- How to figure out if a branch was deleted on merge in Bitbucket Server
- Repository notifications
- Using repository hooks
- View and configure the audit log
- Commit history
- How to identify a deleted branch
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- Missing Commits in Bitbucket Server
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- Compare branches, tags, and commits