Feature Request: Start/Stop Running Timeslips


#1

Greetings FreeAgent,

I am attempting to develop a Desktop application that handles the ability
for me to start and stop, create and remove current running timers with
quick ease in the Task bar.

I started a basic application to see if the timeslips API endpoint yields
enough data, but unfortunately I find there happens to not be enough data
in the timeslips endpoint to understand if a timer is currently running or
not. A simple addition would be two columns in the timeslips response.

{ “timeslip”:
{
“url”:“https://api.freeagent.com/v2/timeslips/25”,
“start_timeslip”: “https://api.freeagent.com/v2/timeslips/25/start”, // <-- new addition
“stop_timeslip”: “https://api.freeagent.com/v2/timeslips/25/stop”, // <-- new addition
“project”:“https://api.freeagent.com/v2/projects/1”,
“task”:“https://api.freeagent.com/v2/tasks/1”,
“billed_on_invoice” : “https://api.freeagent.com/v2/invoices/7”,
“dated_on”:“2011-08-15”,
“hours”:“12.0”,
“status”: “running”, // <-- new addition.
“last_state_changed_at”: “2011-08-16T13:38:00Z”, // <-- new addition
“updated_at”:“2011-08-16T13:32:00Z”,
“created_at”:“2011-08-16T13:32:00Z”
}
}

Given the new fields, we should be able to determined and calculate the
current running timer.

I also feel there should be a endpoint to POST to to start/stop a
timeslip, examples that would be most simplest.

POST https://api.freeagent.com/v2/timeslips/:id/start

POST https://api.freeagent.com/v2/timeslips/:id/stop

I would add a PR myself if I could.


#2

Greetings Kyle,

Thanks for your message and your thorough suggestions, I agree, adding
support for timer interactions would be of huge value.

As I’m sure you can imagine, we receive quite a lot of improvement
suggestions, so we try to capture them and also track their demand.
As such, I’ve created a new card on our public Trello board, capturing your
request and linking back to this original thread:

I’d be grateful if you could add your “vote” to this card, so we can
measure demand against other API requests.
As a result of your vote, you should also receive a notification when the
card progresses through the development cycle.

Thanks for your feedback!
Dave JOn Wednesday, 29 June 2016 12:06:40 UTC+1, Kyle Welsby wrote:

Greetings FreeAgent,

I am attempting to develop a Desktop application that handles the ability
for me to start and stop, create and remove current running timers with
quick ease in the Task bar.

I started a basic application to see if the timeslips API endpoint yields
enough data, but unfortunately I find there happens to not be enough data
in the timeslips endpoint to understand if a timer is currently running or
not. A simple addition would be two columns in the timeslips response.

{ “timeslip”:
{
“url”:“https://api.freeagent.com/v2/timeslips/25”,
“start_timeslip”: “https://api.freeagent.com/v2/timeslips/25/start”, // <-- new addition
“stop_timeslip”: “https://api.freeagent.com/v2/timeslips/25/stop”, // <-- new addition
“project”:“https://api.freeagent.com/v2/projects/1”,
“task”:“https://api.freeagent.com/v2/tasks/1”,
“billed_on_invoice” : “https://api.freeagent.com/v2/invoices/7”,
“dated_on”:“2011-08-15”,
“hours”:“12.0”,
“status”: “running”, // <-- new addition.
“last_state_changed_at”: “2011-08-16T13:38:00Z”, // <-- new addition
“updated_at”:“2011-08-16T13:32:00Z”,
“created_at”:“2011-08-16T13:32:00Z”
}
}

Given the new fields, we should be able to determined and calculate the
current running timer.

I also feel there should be a endpoint to POST to to start/stop a
timeslip, examples that would be most simplest.

POST https://api.freeagent.com/v2/timeslips/:id/start

POST https://api.freeagent.com/v2/timeslips/:id/stop

I would add a PR myself if I could.


#3

Thanks Dave for taking the time to add this to the board.

As I say, if i could make a PR, it would have been with you yesterday.On Wednesday, 29 June 2016 15:26:16 UTC+1, David Jones wrote:

Greetings Kyle,

Thanks for your message and your thorough suggestions, I agree, adding
support for timer interactions would be of huge value.

As I’m sure you can imagine, we receive quite a lot of improvement
suggestions, so we try to capture them and also track their demand.
As such, I’ve created a new card on our public Trello board, capturing
your request and linking back to this original thread:

https://trello.com/c/7i0uIDZR/39-add-support-for-interacting-with-timeslip-timers

I’d be grateful if you could add your “vote” to this card, so we can
measure demand against other API requests.
As a result of your vote, you should also receive a notification when the
card progresses through the development cycle.

Thanks for your feedback!
Dave J

On Wednesday, 29 June 2016 12:06:40 UTC+1, Kyle Welsby wrote:

Greetings FreeAgent,

I am attempting to develop a Desktop application that handles the ability
for me to start and stop, create and remove current running timers with
quick ease in the Task bar.

I started a basic application to see if the timeslips API endpoint yields
enough data, but unfortunately I find there happens to not be enough data
in the timeslips endpoint to understand if a timer is currently running or
not. A simple addition would be two columns in the timeslips response.

{ “timeslip”:
{
“url”:“https://api.freeagent.com/v2/timeslips/25”,
“start_timeslip”: “https://api.freeagent.com/v2/timeslips/25/start”, // <-- new addition
“stop_timeslip”: “https://api.freeagent.com/v2/timeslips/25/stop”, // <-- new addition
“project”:“https://api.freeagent.com/v2/projects/1”,
“task”:“https://api.freeagent.com/v2/tasks/1”,
“billed_on_invoice” : “https://api.freeagent.com/v2/invoices/7”,
“dated_on”:“2011-08-15”,
“hours”:“12.0”,
“status”: “running”, // <-- new addition.
“last_state_changed_at”: “2011-08-16T13:38:00Z”, // <-- new addition
“updated_at”:“2011-08-16T13:32:00Z”,
“created_at”:“2011-08-16T13:32:00Z”
}
}

Given the new fields, we should be able to determined and calculate the
current running timer.

I also feel there should be a endpoint to POST to to start/stop a
timeslip, examples that would be most simplest.

POST https://api.freeagent.com/v2/timeslips/:id/start

POST https://api.freeagent.com/v2/timeslips/:id/stop

I would add a PR myself if I could.


#4

Hi Kyle,

I’m happy to announce that we’ve just added timer support to the API, and it’s pretty similar to what you’d sketched out - hopefully this will allow you to move forward with your app.

See the announcement for details: Support for timeslip timers added to the API

Regards,
Paul.