Cost rates are not imported properly when importing a team from Folio to Folio


Steps to reproduce:
1) create a Folio Test1
2) create a team member John with two cost rates. First: effective date 2015-01-01 and value 20, second: effective date 2015-03-01 and value 25.
3) create another Folio Test2
4) go to the Team tab and use import data function (key shortcut "i")
5) select "folio to folio" import type
6) import the data from Test1

John after the import is going to have only one cost rate in Folio Test2 with the value of 20 and with effective date set to the current date, so both values are invalid.


Jira 6.3.7, every web browser


Marc-André Thibodeau
March 18, 2015, 2:12 PM

Hi Marcin,

First of all, there is indeed a bug in the Folio copy/team import when copying allocations and wages. It has been fixed and will be packaged in the upcoming 7.3 release (due at the end of this week). The bug causes some rates and allocations to be ignored when imported to a folio with a different timeframe.

That being said, note that only the portion of the allocations and rates that is included in the destination folio is imported. And in the case where the timeframe of the Folio you import to has no intersection with any of a team member's allocation periods, then the team member will be imported and automatically assigned a 100% allocation for the whole timeframe of the Folio. So in these cases, it is possible to originally have a team member with more than one allocations/rates that ends up with fewer allocations/rates after the import.

I hope this helps!


Marcin Graczyk
March 19, 2015, 10:38 AM

Hi Marc,

Thank you for your quick response. I haven't mentioned that both Folios (test1 + test2) have the same dates (same time frames). Your answer from the first paragraph satisfies my needs, I'm looking forward to 7.3 update.

You can resolve this issue as a duplicate of the original bug if it was already found by someone else.

Best regards,

March 28, 2015, 2:40 PM

Tempo Update - 28 March 2015

Hi everyone,

This issue is for view only since it has been copied to Tempo Cloud instance, as Folio is now part of the Tempo family.

Issue reporter has been created but if you are a watcher please sign up and continue to watch this issue.

Thank you so much for your feedback.

Kind regards,

The Tempo Team




Marcin Graczyk


Affects versions