timeentry add does not accept a rate

getroadmap / roadmap-api

API documentation for Roadmap

3 stars 2 forks source link

timeentry add does not accept a rate #3

Closed bglase closed 10 years ago

bglase commented 10 years ago

Posting {"ProjectID":593126,"ResourceID":663665,"Date":"2014-08-03","Time":" 4.00 ","Description":"Imported worklog","Rate":87.6,"RoleId":114805,"TodoItemID":12442111}

returns a 200 status, with { "ID": 2244667, "ProjectID": 593126, "ProjectName": "Takata MSB Controller", "ProjectCustomCode": "14CS02", "ProjectCode": "14CS02", "MilestoneID": null, "TodoItemID": 12442111, "ResourceID": 663665, "ResourceName": "Tanya O'Connor", "ResourceCustomCode": "O'CONNOR, TANYA", "ResourceCode": "O'CONNOR, TANYA", "RoleID": 114805, "RoleName": "Program Manager", "Date": "2014-08-03T00:00:00", "Time": 4.0, "Description": "Imported worklog", "Rate": 111.6800 }

I was hoping the posted rate would appear in the 'adj rate' column of the time entry.

bkingbking commented 10 years ago

@bglase Rates are applied globally at the role level (std rate). It can be overridden at the project level (i.e. adj rate). For example, suppose Bill is an Account Manager, and the standard rate for Account Managers is $100.

If Bill logs 10h against any project, that will yield $1,000
However, suppose Bill has an adjustable rate of $90 for Project ABC, that will yield $900. Thus, adjusted rates is exceptions based.

Here's a summary of how it works from our support pages.

@davejclausen Please step in if the API is expected to behave differently than the UX layer.

bglase commented 10 years ago

Got it, thanks. Makes sense, just wasn't what I was hoping. I can work with it. The tracking of project 'actuals' is relatively basic in Roadmap - if it were to be enhanced, I'd suggest allowing actual rates to be overridden on a timeentry, and also a way to track non-labor (e.g. material costs) like a budget against actuals.

bkingbking commented 10 years ago

@bglase Thanks for the feedback. Will have to think this one through because a lot of clients would go bonkers if we allowed users to adjust rates on a per time-entry basis. They don't always want resources to know their billing rate, let alone give them the option to get it wrong!

Our product roadmap includes support for non-labor costs, as well as the ability to flag individual tasks as non-billable.

bglase commented 10 years ago

Right - I suppose overriding the rate would only be useful for syncing (e.g. loading) entries from another system, through the REST API for instance

On Aug 12, 2014, at 3:59 PM, Bill King notifications@github.com wrote:

@bglase Thanks for the feedback. Will have to think this one through because a lot of clients would go bonkers if we allowed users to adjust rates on a per time-entry basis. They don't always want resources to know their billing rate, let alone give them the option to get it wrong!

Our product roadmap includes support for non-labor costs, as well as the ability to flag individual tasks as non-billable.

— Reply to this email directly or view it on GitHub.