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.

Folio Configuration

Owned by JeanH (Deactivated)
Jan 08, 2014

The Portfolio menu is visible if and only if the logged in user can browser at least one projet

The Configuration

The configuration of a folio can easily be  accessed via the "Configure" menu item of the "Folio" menu at the top right of your FOLIO pages. It can also be accessed via the "Configure" menu item of the "Cog" of a folio listed in the Manage screen. ONLY the owner or administrators of the FOLIO will have the rights to update any fields of the folio's configuration.

 

  • From the "Folio" menu when you are in a folio (from Tool cog > Configure)

  • From the "Cog" menu of the folio's when in the Manage Portfolios page (from "Portfolio" Menu > Manage portfolios)



Folio Basic Information

Where:

Associated board is the GreenHopper board (Scrum or Kanban ) associated to the folio.
Most of the configuration settings of the folio will be driven by the board's configuration settings such as:

  • The query of the saved filter defining the scope of the folio will be synchronized with the board's saved filter query - will be editable only via the board's configuration
  • The Earning field will be initially set with the Estimation field defined by the board - can be overridden
  • The Earned Issues will be synchronized with the last column mapping of the board - will be editable only via the board's configuration
  • The Hours per day will be synchronized with the board's hours per day - will be editable only via the board's configuration
  • The Week days will be synchronized with the board's week days - will be editable only via the board's configuration
  • The  None working dates will be synchronized with the board's hours per day - will be editable only via the board's configuration

 

FOLIO supports GreenHopper 6.1.1 and higher only.
If FOLIO does not have Agile enabled you can enable it via the action cog at the top right of your FOLIO's configuration screen.
To be able to link boards to your folio you must be able to see at least one GreenHopper board.


Owner is the owner of the board. The owner is the only person with the permissions to add, remove or update expenses, positions or team members.

 

Changing owner does not automatically set new owner rights to the saved filter. Therefore . must give the proper saved filter rights to the new owner (see 'Sharing a filter' section from JIRA saved filters documentation).


Start date and End date defines the boundaries of the folio.


Scope

The folio scope is a list of specific project goals, deliverable, tasks, costs and deadlines.
In FOLIO the project tasks are defined by a JIRA saved filters providing maximum flexibility.
Unless the folio is associated with an Agile board the query of the saved filter can be modified at anytime.

Earning rules

The earning rules will dictate when the tasks will be considered as earned and which field will be used to weight the task.

Earned Value Field

The Earned value field is the numeric parameter that FOLIO will use to determine the earned value of an issue.
For instance:

  • Original Estimate: The number of estimated hours will be used.
  • Issue count: Every issue will have the same earn value.
  • Any other JIRA Numeric custom fields: The value of the field will be used. (See how to add custom field)

Earned Issues

The Earned Issues defines the state that an issue needs to meet to be considered as earned.
One or more JIRA statuses can be part of the earned issue definition.
If no statuses are selected FOLIO will consider issues earned if these a flagged as resolved.

 

To be earned, the issue must meet the earned issue definition within the folio's time frame.
e.g: An issue that will be resolved after the end date of the folio will not be considered as earned for the folio.

 

Accounting

Profitability

Allows for tracking revenues in a folio. When checked, a Revenue tab will be displayed between Cost and Team tabs. This new tab lets you to specify actual revenues of that particular folio.

When this option is selected, the option to User revenue as Actual Value is offered to you. This option should be selected if the budget of this Folio is your customer's budget (the money the customer is planning to be paying to your service company) rather than your company's budget for the project. In that scenario, EVM performance metrics will only make sense if they are calculated by comparing the budget to what your customer is actually paying: your revenue. Selecting this option has the following consequences:

  • Makes information entered in Revenue tab to be used to calculate Actual value over time, and thus calculate EVM metrics.
  • A note will be displayed in Overview indicating that Actual Value is based on Revenue
  • Budget Variance report will be showing yellow bars representing revenues per type instead of red bars representing costs per type
  • Earned Value report will be showing yellow bars representing revenues per period instead of red bars representing costs per period

Reserve

Management reserve is for unforeseen risks.  It is a percentage of the total budget.

Contingency

Contingency is for known risks. It is a percentage of every expense's payment.

Tolerance

Tolerance percentage for the folio's performance indices.
It defines a warning state (yellow) for the indices before turning hot red!  

Currency

Defines the currency that will be used across the folio.

 

Folio Permissions

A folio is visible and editable by its owner and all its administrators.
It can be shared in "read-only" by simply sharing the JIRA saved filter (see 'Sharing a filter' section from the JIRA saved filters documentation).

 

In the case where the JIRA filter or the owner of a folio was removed from JIRA, all JIRA administrators will gain access to the folio so that a new JIRA filter or owner can be re-assigned.

 

Expense / Revenue / Team Fields

You can add custom fields to your Actual expenses , Revenues , Consulting Revenues and your Team members.
Their value can be set in the creation dialog or in the update dialog of the related entries.
They will be available in read mode in the detail columns .


 

These fields will be injected into the Excel export.

Removing an expense field

Removing an custom field will remove it permanently from the folio and all its associated values.

 

Working Days

Unless that the folio is associated to an Agile board, the hours per week, the week days and the non-working dates can be defined per folio via the Working Days tab. FOLIO will use these settings in most of its evaluations, forecasts and charts.

 

Worked hours

By default FOLIO will evaluate the worked hours of a team member based on its availability defined in the member's wage table.
The owner can manually override the computed hours with a specific value for a specific period for each team member via the worked hours table.
If JIRA is used to track time spent on the issues (using JIRA itself or any other Time tracking add-ons such as Tempo) FOLIO can be set to retrieve the team members worked hours directly from the issue worklogs by enabling the "Synchronize with JIRA's work logs" option.

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 page.

Switching from an option to the other will remove all manually entered worked hours for all affected users.

Hours per Day

Number of working hours per day (Default JIRA Hours per Day settings)

Working Days

Working days per week (Default JIRA Days per Week settings)

Non-Working Dates

A non-working date such as a public holiday.

 

JIRA Agile (GreenHopper) Integration

FOLIO automatically detects JIRA Agile (GreenHopper) when starting up. Although if FOLIO fails to connect to GreenHopper you can force the connection with the "Enable Agile Support" menu item from the configuration action menu in the top right corner.

 

 

 

On this page:

Related pages: