FOLIO contains all needed components to monitor the statuses of a project or group of projects. All project managers must juggle with time, scope and budget; the well-known constraint triangle. FOLIO will help you with those critical aspects by letting you plan a budget, define a scope and a time frame. Create a PortfolioFirst time in FOLIOThe first time you log in FOLIO, the getting started page will be displayed and you will be able to create your first portfolio from this screen via the "Create a new portfolio" link. Note that you will have access to the user guide, the latest release notes and many more useful sites via this page. The getting started page will always be accessible via the main FOLIO menu.
To access FOLIO simply click on the FOLIO menu in the your JIRA header
Thereafter in FOLIOYou can create a portfolio by clicking the "Cog" menu and by selecting the Create item. Note that the Tool Cog is available in all FOLIO pages.
How to create a portfolioFour different approaches are available when you create a portfolio: 1. JIRA Projects Use this approach when the scope of the portfolio is based on one or more existing projects in JIRA. To select more than one project, click the arrow again of the project field and select a second project name and then a third etc. Promote this approach to include the entire issues from one or more projects. Image Removed Note that FOLIO will create a saved filter based on the selected project(s), the newly saved filter will be named like this "Filter for Portfolio : YOUR_FOLIO_NAME - 1" Image Added Info |
---|
FOLIO will automatically create a JIRA saved filter that will be owned by the user creating the portfolio. The filter can be seen in the portfolio's configuration under the scope tab. The filter will be private but can be easily shared via the edit shares of the JIRA saved filters. |
2. AdvancedUse this approach when the scope of the portfolio is based on an existing JIRA saved filters. A JIRA filter helps to regroup issues with specific characteristics from one or more projects Promote this approach to include selected issues if the issues defining the scope have specific characteristics and are from one or more projectsImage Removed Image Added Info |
---|
FOLIO will automatically create a JIRA saved filter that will be owned by the user creating the portfolio. The filter can be seen in the portfolio's configuration under the scope tab. The filter will be private but can be easily shared via the edit shares of the JIRA saved filters. |
3. ScrumUse this approach when you want to track a project based on an Agile Scrum Board. The scope will be defined by the filter of the Scrum board and most of the portfolio's configuration settings such as the working days and the earning rules will be driven by the board's configuration settings avoiding any duplication. Promote this approach to include link your portfolio to your Agile project. Image Removed Image Added Info |
---|
FOLIO will automatically create a JIRA saved filter that will be owned by the user creating the portfolio. The filter query will be kept in synch with the GreenHopper's board filter query. The filter will be private but can be easily shared via the edit shares of the JIRA saved filters. | 4. KanbanUse this approach when you want to track a project based on a Kanban Board. The scope will be defined by the filter of the Kanban board and most of the portfolio's configuration settings such as the working days and the earning rules will be driven by the board's configuration settings avoiding any duplication. Promote this approach to include link your portfolio to your Kanban project.
Info |
---|
FOLIO will automatically create a JIRA saved filter that will be owned by the user creating the portfolio. The filter query will be kept in synch with the GreenHopper's board filter query. The filter will be private but can be easily shared via the edit shares of the JIRA saved filters. |
Anchor |
---|
| FieldDefinition |
---|
| FieldDefinition |
---|
|
Portfolio Name | Use whatever you want for your Portfolio name (special characters, numbers, etc. are allowed). There is no special requirement in the naming convention of a portfolio. |
---|
Scrum Board | In the case of a Scrum board association, Select a Scrum board Note only the Scrum board that you can see will be available as an option |
---|
Kanban Board | In the case of a Kanban board association, Select a Kanban board Note only the Kanban board that you can see will be available as an option |
---|
Start Date | This is the date from which you want to start reporting expenses and positions in a portfolio. Note that this date has no impact on the date of issues you have in the JIRA project or the saved filter. To limit the JIRA project scope, set a restriction on dates in your JIRA saved filter. |
---|
End Date | This is the date the portfolio ends. This is a critical date since it gives the pace of progress the team should maintain to successfully complete the portfolio scope. Note that this date has no impact on the date of issues you have in the JIRA project or saved filter. To limit the JIRA project scope, set a restriction on dates in your JIRA saved filter. |
---|
Worked Hours | Select this option if you want the team members worked hours to be taken directly from the work logged of JIRA. Note that all team members will be synchronized with JIRA's work logs by default. This setting can be overwritten individually directly from the team member's page. |
---|
Description | Give a description of the Portfolio, if require |
---|
Scope | Confirm the scope of the portfolio by selecting the appropriate: JIRA project(s) for Preset or Existing JIRA saved filter for Advanced (Note: clicking on Edit Filter link bring you to JIRA Edit Filter page |
---|
Changing The Portfolio DatesThe start date and end date of the portfolio can also be edited directly from any portfolio pages by clicking on the date itself in the upper right left corner of the page. Image Removed Image Added
|