-
-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import project "budget" field #841
Comments
Hm, indeed you are right. I missed that field...
|
That worked Kevin. Now the next problem I have is that we had the Budget value as being the number of hours estimated that are required to get a job done. Because I have a fixed rate for each project, if I use Hours budgeted it should be able to automatically calculate the total in $ spent. The trouble is, I think the "budget" field is used in the program as $. My next step is to look for other calculations to see where or how difficult it would be to change that from a $ value to an hours budgeted value, but that sounds harder than it's probably worth. I may need to tackle it from the import side where I do the calculation on import so the budget field is in $. Clint |
The field is displayed in the customers currency, so in your case likely dollars. |
I am currently working on the budgets. |
Regarding the importer, I simply used the code you had suggested and it worked correctly. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai. |
Hello, I am importing data from Version 1.31 and in reviewing the import code I see that the "budget" field is unsupported. Does anyone have any guidance for me where I could start in including this field in the import or what mods I would need to make? I have tons of projects in my old database where I would like to carry over the budget value into the new db. Even if it is moving it into an integer or something.
Thanks!
Clint
The text was updated successfully, but these errors were encountered: