From: Ihor Radchenko <yantar92@gmail.com>
To: Eduardo Suarez <esuarez@itccanarias.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Manual Ordering and Dynamic Priority
Date: Fri, 02 Sep 2022 20:52:26 +0800 [thread overview]
Message-ID: <87fshalz05.fsf@localhost> (raw)
In-Reply-To: <20220831161348.GA2413557@itccanarias.org>
Eduardo Suarez <esuarez@itccanarias.org> writes:
> I have lots of tasks (todos) and I would like to create a long backlog based on
> my perceived priority.
>
> I was thinking to deal with them in the following way:
>
> - divide them in groups (categories or similar),
> - manually sort priority for every group,
> - mergesort groups, that is, start merging groups in pairs, and manually sort
> for every step the union group until I have a large sorted backlog.
>
> For this to be practical, I would need an easy way to sort manually a group of
> tasks and get them assigned automatically a priority (or any other hack) so
> that priority ordering matches manual ordering.
>
> Any idea about how to get this done?
It sounds like you just want to have a list of active projects and
select one top-priority task at a time from each project. The projects
can be simply a headline with all the tasks listed as children.
I do not recommend assigning priority as a number. From my experience,
it is much easier to order the tasks manually inside a project. You will
need to re-order things as the project progresses anyway. Fiddling with
numbers will quickly become unmanageable.
I also do not recommend listing _all_ the tasks. It is much more
productive (again, from experience) to list the one top-priority task
for each project and nothing more until you finish the current task
batch. In GTD, this is usually done by assigning NEXT todo keyword to
the top-priority task, while all others are assigned as TODO. You may
also leverage org-edna package to flip TODO->NEXT once you complete the
current NEXT task.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-09-02 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 16:13 Manual Ordering and Dynamic Priority Eduardo Suarez
2022-08-31 16:27 ` indieterminacy
2022-08-31 21:42 ` Tim Cross
2022-09-09 10:01 ` Rudolf Adamkovič
2022-09-09 22:05 ` Tim Cross
2022-09-10 8:17 ` Eduardo Suarez-Santana
2022-09-02 12:52 ` Ihor Radchenko [this message]
2022-09-06 9:15 ` Eduardo Suárez
2022-09-07 4:45 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fshalz05.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=esuarez@itccanarias.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).