Kitologic is proud to announce the release of FOLIO 3.5, Folio's biggest release since its launch . Folio 3.5 introduces the report section with the two most requested reports, the indexes tolerance and the per portfolio and more flexible working days.enabling you to: This release also includes a number of improvements and fixes. The Steering Committee Report - Because it is all about visibility!
See past project status and indices variation over time by consulting the Steering committee report The steering committee report presents a summary of the portfolio's status using various showing you the usual financial and health metrics at a you get in the portfolio's overview, at any given point in time. The report allows you to see the variation of the indexes since an ulterior indices variations to another date via the 'Compared to' date parameter. It is also offered in a printable view. Image Removed The Expense Report - Know where your money goes!The expense Variations are colored in order to indicate if the change is good (green), requires vigilance (yellow) or is bad (red). You can also get it in a printable version from the report's action menu or by hitting "p" while consulting it.
Image Added Better track how your money is spent by consulting the Expenses reportThe Expenses report presents a uniform and accurate report of expenses for a given time frame. The report can be generated for both the planned and the actual expenses. It is highly configurable and can be exported in Excel or be printed directly in HTML. Image Removed Define your Working DaysThe week days and hours per week are now more flexible and can be set per portfolio. Their default values are based on the JIRA Timetracking but can easily be changed via the portfolio's configuration to better match your needs. Image RemovedWhat is your Tolerance?In the accounting configuration we have added the new tolerance setting; a designated percent of your portfolio's health indexes that will be tolerated before becoming red. Your portfolio's health indexes will turn yellow when the tolerance mark is reachedactual expenses in a variety of ways by setting any or all of the many parameters it offers. And as you can expect, you can get a printable version of it using the report's action menu or by hitting "p" while consulting it.
Image Added Create your own reports by exporting the Expenses report to an Excel spreadsheetThe Expenses report can be exported to Excel format to give you all the latitude you need to further digest, analyze or graph the data. Do it by selecting the "Export to Excel" item in the report's action menu found on the top right of the report's parameters panel. The parameters that were used to generate the report can be found on the second tab of the generated spreadsheet. Image Added
Configure different time tracking options per portfolioThe working week days and number of hours per normal working day can now be set for each portfolio, giving you more flexibility to handle various working schedules. Of course, you will not be required to configure these for each and every portfolio, since the default values used are the ones defined in JIRA's Time tracking configuration.
Image Added State your tolerance to get better progression of warning level on health metrics In the portfolio's accounting configuration we have added a new tolerance setting; a designated percentage of your portfolio's health indices that will be tolerated before turning red. While in the tolerated range, your portfolio's health indices will turn yellow, clearly indicating that these require your attention, but not lighting the fire alarm too quick.
Improvements Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-97 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-98 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-96 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-99 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-100 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-104 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-107 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-108 |
---|
| Bug Fixes Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-103 |
---|
|
Jira Legacy |
---|
server | JIRA (greffon.atlassian.net) |
---|
serverId | 61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e |
---|
key | FOLIO-106 |
---|
|
|