← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 724201] Re: Cannot use the timesheet program because of a warning message "Please Enter A Value"

 

** Changed in: openobject-addons
       Status: New => Confirmed

** Changed in: openobject-addons
     Assignee: (unassigned) => OpenERP R&D Addons Team 3 (openerp-dev-addons3)

** Changed in: openobject-addons
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/724201

Title:
  Cannot use the timesheet program because of a warning message "Please
  Enter A Value"

Status in OpenERP Modules (addons):
  Confirmed

Bug description:
  In the section : (Human Resources > Time Tracking > My Timesheet ) I
  have been trying to add an entry to the Time sheet using the "New"
  button available in the "Timesheet" window at the bottom of the
  screen.

  When I click "New" a row is added to the table with "Analytic Account"
  and "Description" highlighted in a deeper blue color, which I have
  read elsewhere that this suggests that they are required fields. If I
  fill both of those fields in (after creating a new Analytic Account) I
  try to commit the changes by clicking away from that row in the table
  or by clicking the little save icon on the far left of the row. I am
  then presented with a message: "Warning Message: Please Enter a
  Value". I attempted to fill in all of the other, non required fields
  but it still will not allow me to commit the changes.

  Apart from the fact that the warning message is not descriptive enough
  to point out what exactly the problem is, I feel that this is a bug
  because I cannot get it to commit any changes to the timesheet.

  I am using OpenERP 6.0 on the trial version on the website. I have
  attached a file with a list of all the modules I have installed. I
  have already been speaking with Alan from the support team and he had
  a quick look into it and confirmed that it was a bug and not a
  workflow issue.



References