emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Eduardo Suárez" <esuarez@itccanarias.org>
To: <emacs-orgmode@gnu.org>
Subject: Re: Manual Ordering and Dynamic Priority
Date: Tue, 6 Sep 2022 10:15:40 +0100	[thread overview]
Message-ID: <20220906091540.GB2201663@itccanarias.org> (raw)
In-Reply-To: <20220831161348.GA2413557@itccanarias.org>

Thanks a lot for all your answers. I've been thinking about it and I've come up
with another solution.

My main problem is, given a file with lots of tasks, to create a "preorder" of
tasks to avoid the fear of missing out tasks when planning or selecting the top
priority tasks. To review the full list of tasks takes very long (my estimate
is O(n^2)). Reordering the current hierarchy is not an option because the file
has already a predefined (deep) structure.

So my solution is simple: create another top level heading in the file named
planning and create a hierarchy of links to tasks in it. Something like this:

* Planning
- [[#task4][My task 4 header]]
  - [[#task5][My task 5 header]]
  - [[#task1][My task 1 header]]
- [[#task2][My task 2 header]]
  - [[#task7][My task 7 header]]
    - [[#task6][My task 6 header]]
  - [[#task3][My task 3 header]]

So I can preorder using dependencies like org mode natural TODO dependencies,
and I get something like a gantt chart (without dates and planning). Moreover,
it looks simple to create a template to add a task to this list. I can even
document the relationship between tasks and priorities there.

Then, it is straightforward to select top priority tasks in this file.
Repeating the same for every agenda file, I can easily select a small list of
tasks to work with (e.g. assigning priorities or a TODO keyword).

next prev parent reply	other threads:[~2022-09-06 10:00 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
2022-09-06  9:15 ` Eduardo Suárez [this message]
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=20220906091540.GB2201663@itccanarias.org \
    --to=esuarez@itccanarias.org \
    --cc=emacs-orgmode@gnu.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

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).