Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Div
stylewidth:100%
idkt-documentation-section
alignleft
Style
#breadcrumb-section {
  	margin-bottom: 10px;
}
#breadcrumbs li,
#breadcrumbs li a{
  	color: #999;
}
#main-header {
 	margin: 10px 0 0;
}
#title-text a {
  	color  : #3B73AF   !important;
}
 
.page-metadata 
{
  transition         : opacity .25s ease-in-out;
  -moz-transition    : opacity .25s ease-in-out;
  -webkit-transition : opacity .25s ease-in-out;
}
.page-metadata 
{
  opacity       : 0;
  margin        : 0 0 30px;
}
 .page-metadata:hover 
{
  opacity       : 1.0;
}
#title-text {
	font-family: "kulturista-web",sans-serif;
	font-weight: 300;
	font-size: 50px;
	line-height: 75px;
	padding-bottom: 5px
}
Div

 

Image RemovedImage Added

Kitologic is proud to announce the release of FOLIO 3.3, enabling you to:

This release also includes a number of improvements and fixes.

Anchor
FOLIO-54
FOLIO-54
Automatically synchronize worked hours with work logged in JIRA

Your team members are logging their work directly in JIRA or using a time tracking plugin? If that's the case, you probably don't want to bother re-entering that information in FOLIO manually. With that new feature, you will now be able to configure your portfolios to have their worked hours taken directly from the work logged into your project's issues.

Go to your portfolio's configuration page and open the accounting tab. Check the "Synchronize with JIRA's work logs." and your done!

Go back to the Team page and see the worked hours of you team members populated with what they logged in JIRA issues associated with that portfolio. If you want a specific member not to be synchronized with JIRA, simply uncheck the "Synchronise with JIRA's work logs" box under his or her worked hours table.

 

Anchor
FOLIO-53
FOLIO-53
Visualize the project's current scope and workload

You can now view to what user stories, bugs and other types of issues your project is associated with (i.e. the scope of the project) and see if the budgeted positions match the effort required for that scope. Answer questions such as:

  • Are the budgeted salaries sufficient to implement the planned features of our cool application?
  • How much required effort has been estimated for the planned scope? How much to fix the known bugs?
  • What's the maximum effort a person can possibly provide given the current portfolio's time frame?

In the Budget page, clicking the scope icon () next to the Budget total brings that information in the details panel on the right.

Anchor
FOLIO-37
FOLIO-37
Use FOLIO with JIRA 6.0

FOLIO is ready for JIRA 6! You won't need to wait to continue using FOLIO when you upgrade to the next generation of JIRA, of which a beta is already available for download. This also prepares FOLIO for OnDemand. Let us know if you would like to be kept updated about FOLIO's availability for OnDemand. Or simply watch the related issue in our JIRA.

Anchor
Improvements
Improvements
Improvements

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-58

Anchor
Fixes
Fixes
Bug Fixes

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-44

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-59

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-60

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-62

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-64

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-65

Jira Legacy
serverJIRA (greffon.atlassian.net)
serverId61fe9a0f-ef13-3ad4-8d07-34670cf0ed8e
keyFOLIO-67