Dan Rice

Does the "set the date the action should be shown" option completely solve this for you? Is it just a case of adjusting the wording to be more explanatory?

_On November 11, 2012 at 09:03:07 (-0800), zoombody commented:_ The dropdowns are indeed tedious. This ticket could be made more generic -- I think there is probably a better solution...

_On November 11, 2012 at 09:04:40 (-0800), zoombody commented:_ Moving this to someday/maybe, which is SOP for enhancements until prioritized for a release

_On November 11, 2012 at 09:11:33 (-0800), zoombody commented:_ Actually, I like this ticket. Upping the priority from someday/maybe.

_On November 11, 2012 at 07:21:08 (-0800), maddentim commented:_ +1 from me as well. I thought there was a ticket out there for this already but I could not find...

_On November 11, 2011 at 11:39:41 (-0600), popsch commented:_ Btw. if currently use #name with an existing context, then you will get the following error message: ActiveRecord::StatementInvalid in TodosController#create SQLite3::ConstraintException:...

_On November 11, 2011 at 20:19:42 (-0600), popsch commented:_ Also, I think a similar thing is true for the project and project_id.

_On November 11, 2011 at 08:25:17 (-0600), lrbalt commented:_ (In [[r:50bc2623d9f3925c3351fd5d3fd3ac6102114804]]) fix #1224. Allow existing and non-existing project/context names in REST API Branch: master

_On November 11, 2011 at 08:26:42 (-0600), lrbalt commented:_ should work now, see the examples in the todo_xml test in the commit.

_On November 11, 2011 at 09:20:51 (-0600), popsch commented:_ part way there. I was also suggesting to deprecate #id in favour of #id to go along with the other method...