Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new task from home page adds task at end rather than sorting #938

Closed
dnrce opened this issue Jun 25, 2014 · 8 comments
Closed

new task from home page adds task at end rather than sorting #938

dnrce opened this issue Jun 25, 2014 · 8 comments
Labels
bug 🐛 Problems with the code that result in unexpected or bad behavior
Milestone

Comments

@dnrce
Copy link
Member

dnrce commented Jun 25, 2014

Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/938

If you create an action from the home page it appears at the bottom of the relevant context rather than being sorted into the proper spot. This is similar to bug #393 (resort on edit)

Originally reported by Ben Jackson on September 9, 2009 at 10:58:02 (-1000) against version git-devel

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On September 9, 2009 at 14:32:48 (-1000), epall commented:

What do you mean by "sorted into the proper spot"? GTD doesn't really have a concept of "ordering" for anything, so Tracks doesn't, either, at this point. We have a patch in the pipeline for manually sorting tasks, so maybe its time us core GTD folks give up this bit of ground and let people actively "order" tasks.

@dnrce dnrce added this to the Someday/Maybe milestone Jun 25, 2014
@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On September 9, 2009 at 15:13:22 (-1000), Ben Jackson commented:

I guess at the most basic what I mean is that if you do something like add an action from the Home page, the AJAX-y update of the page should make it look like it would if you reloaded it. In particular if you create a new action with a due date, it is placed at the bottom of the appropriate context even if a reload would (because of the due date) display it at the top of the context.

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On September 9, 2009 at 15:18:28 (-1000), epall commented:

Okay, that makes sense. Any chance you could write up some tests for it so I've got a target to hit?

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On September 9, 2009 at 15:32:06 (-1000), Ben Jackson commented:

Unfortunately I don't know anything about rails. I installed it a couple of days ago to try tracks. I will probably learn about rails if only to hack on tracks, but I don't know when I'll get to it. Perhaps I should add a project to remind me...

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On September 9, 2009 at 15:37:10 (-1000), epall commented:

Tracks was one of my first Rails projects, and I believe a learning experience for the other maintainers, as well. It's getting a bit crufty, but with the TLC I'm giving it right now and some more help it should be a lot cleaner soon. I think it's a great project to cut your teeth on Rails with, and writing tests is a great way to get your feet wet.

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On September 9, 2009 at 20:03:43 (-1000), Ben Jackson commented:

This also happens if you edit a task and change the context. The task moves to the other context "live", but does not sort by due date.

@dnrce
Copy link
Member Author

dnrce commented Jun 25, 2014

On December 12, 2009 at 05:34:36 (-1000), epall commented:

I've got too many tickets at this point

@dnrce
Copy link
Member Author

dnrce commented Jul 11, 2014

Duplicate of #256

@dnrce dnrce closed this as completed Jul 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Problems with the code that result in unexpected or bad behavior
Projects
None yet
Development

No branches or pull requests

1 participant