This is the documentation for an older version of Folio and has been moved to the Tempo instance.
Please view the Folio Category in the Tempo Products Wiki Categories for all versions of Folio's Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

 

 

A Portfolio modification can be done at any time. Results of this change are instantly available on all screens.

Use this option to check any impacts a change may have on a project.

You can access the portfolio configuration screen from:

  • Manage Portofolios page (from FOLIO Menu > Manage portfolios)

  • Tool Cog ( ) when you are in a portfolio (from Tool cog > Configure)

By either way, you get the above page:

Portfolio Basic Information

Clicking on portfolio fields allow you to modify them (see Create Portfolio for more info on portfolio fields)

Note that if you are not a JIRA Administrator the following warning will be displayed when clicking on Owner field.

Changing owner does not automatically set new owner rights to the saved filter.

Therefore you must give the proper saved filter rights to the new owner (see 'Sharing a filter' section from JIRA saved filters documentation).


Scope

The portfolio scope is whatever JIRA can regroups and provides since FOLIO is directly linked on JIRA saved filters or projects.

Scope can be:

    • A single project with its issues

    • Many regrouped projects with their structure and issues

    • A filter you saved in JIRA that regroups issues with specific characteristics

    • Etc.

The portfolio scope is whatever JIRA can regroups and provides since FOLIO is directly linked on JIRA saved filters or projects.

At any time you can change the scope of your portfolio by changing the saved filter. To do so, click on :

 

 

 

Portfolio Visibility

Only the portfolio owner can change configuration and modified budget, team member or actual.
The owner can give visualization access to a portfolio by sharing the portfolio saved filters (see 'Sharing a filter' section from JIRA saved filters documentation).

Earning rules

The earned value gives the advancement progress of the project. It is based on a specific JIRA field you configure and it is earned when it gains a resolution status you also configure (ex. issue with a “resolved” status is consider to be earned while an issue with an “opened” status is still a not earned issue). 

 

 

Earned Value fields

The Earned value (EV) is by default based of the original estimates of the issues but can be set to be based on the issue count (all issues will have the same earned value) or any number custom fields defined in the JIRA administration section.

JIRA Original estimate

The earned value is time based. Time (original estimate) of all issues is added and provides a total original estimate. Budgeted amount is divided by the total time originally estimated to complete the work. When an issue has the resolution status defined as earned, its proportionally becomes an earned value.

Issue count

Project manager considers that all issues have a same weight to measure the advancement progress of the project. Budgeted amount is divided by the total number of issues. When an issue has the resolution status defined as earned, it becomes an earned value.

Create a custom field Business Value, Story points,...

To create a custom field in JIRA, see the following instructions page Create custom field.

For example:

A business value is given to each JIRA issue with a worth for the project. Issues with important impact on the project (i.e. impact on the deliverable, complexity of the issue, etc.) should be categorized as issues with high business value. Budgeted amount is divided by the total business value. When an issue has the resolution status defined as earned, its proportionally becomes an earned value.

 

Earned issues

To be earned, an issue needs to get a specific resolution status. Confirm the resolution status (one or more) that an issue should have to be considered as an earned value.

Accounting

Worked hours

Select "Synchronize with JIRA's work logs" if you want the team members worked hours to be taken directly from the work logged into 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.

Reserve

This is for contingency and/or management reserve.  

If required, set a percentage of reserve that will be calculated on the total budgeted expenses. This amount is not included in the total budgeted amount but is displayed in the forecast chart.

Currency

Select the currency you wish to work with. By default, the current currency is based on the JIRA locale server setting.


  Non working days 

A non working day is a day where all team members are not working and not paid. When a day is identified as being a non working day, it is not included in the project number of days for completion nor in the remaining days on the project.

 Set non working days 

Click on dates that are non working days.

You can get previous and following months by clicking the left and right arrows.

Note that click 'Clear all non working days' if you want to remove all non working days

 



Vacation of a team member

Access the team functionality and modify the availability of the team member for a day or a specific period of holidays. 

 
The work schedule is a component of JIRA. To change the work schedule go to Configure JIRA Time tracking.

 

 

 

On this page:

Related pages:

  • No labels