Leave request not calculating correct the number of days

Bug #812303 reported by TArpi
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Wishlist
OpenERP R&D Addons Team 3

Bug Description

Sys: OERP 6.0.2, Ubuntu 10.10.

If an user introduces in Human Resources> Leaves> Leaves request a new request the Number of days are not calculated correct.

To test:
1. Create an employee.
2. Introduce a new leave request with start date: 07/18/2011 08:00:00 stop date: 07/29/2011 17:00:00

Result: it calculates 12 day, witch is OK if we take calendaristic days, but not for an employee.

Expected: to calculate 10 day, accordingly for example to the working day in Project/Configuration/Resources/Working time

Thanks,
TArpi

Tags: maintenance

Related branches

Amit Parik (amit-parik)
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
TArpi (teksearpi) wrote :

Hi Amit Parik,

Thank you for your fast response.

I think if the Leaves Request depends from the Working time, then the hr_holidays module should depend from project_long_term when installing.

And we should have a menu in Human Resources > Configuration > Leaves pointig to the Project> Configuration > Resources>Working time (as we have for example in Sales an Purchases menu for Products submenu)

Should I open a new bug for these, or you will "arrange" ? :)

Thanks,
TArpi

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello TArpi,

I am agree with your another above improvement regarding hr_holidays.

@R&D Team3:

Would you please consider the above mention point for usability purpose.

I think for the solution of these bug if the leave request will consider the working time then we need to consider above suggestion.

Thanks.

Revision history for this message
Mustufa Rangwala (Open ERP) (mra-tinyerp) wrote :

Tarpi,

yes we are working for hr holidays improvement.
And the problem will be solved soon.

There were already one feedback available on http://feedback.openerp.com/forums/87923-human-resources for the same issue.

Anyway thanks for reporting,
mra

Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Meera Trambadia (OpenERP) (mtr-openerp) wrote :

Hello TArpi,

Its fixed in https://code.launchpad.net/~openerp-dev/openobject-addons/trunk-bug-812303-mtr
Revision ID: <email address hidden>
Revision no: 4984

And to have a Resources->Working time menu you need to report a new bug..:)

Thanks,
mtr

Changed in openobject-addons:
status: In Progress → Fix Committed
Revision history for this message
Mustufa Rangwala (Open ERP) (mra-tinyerp) wrote :

Hello,

Thanks Meera for your fix, but we can not implement/apply it for 6.1.

@ Tarpi, its really good idea to have working time synchronize with leave request. We will definitely consider it for future release.

I am setting bug as wishlist for now.

Regards,
Mustufa

Changed in openobject-addons:
status: Fix Committed → Confirmed
importance: Low → Wishlist
Revision history for this message
Geoff Gardiner (geoff-gardiner) wrote :

There is a strange process in this - the calculation of request days can be left behind even if the date is corrected.

So if the end date is set BEFORE the start date (which is an error in my opinion) then this is not corrected if the end date is set AFTER the start date.

So to save a corrected date form you must also delete the number of requested days if it shows negative. This is an error.

Revision history for this message
Geoff Gardiner (geoff-gardiner) wrote :

And I think that this has changed after I wrote the comment - since I was using Anthony Lesuisse's system as a server I don't know what versions he had except that this was 'the latest 6.1' and I have no access any more.

tags: added: maintenance
Revision history for this message
Pierre Lamarche (www.savoirfairelinux.com) (pierre-lamarche) wrote :

Any update ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.