From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Incident tracking
Date: Fri, 28 Feb 2020 00:28:06 +0100 [thread overview]
Message-ID: <20200227232806.GF16935@volibear> (raw)
In-Reply-To: <CAFAhFSUxTLUD5qUGxDxcjaey2RC6tRs6mRvntABNg9Lzoa3XcQ@mail.gmail.com>
On Thu, Feb 27, 2020 at 04:55:30PM -0600, Lawrence Bottorff wrote:
> What would be the best way in the Emacs org-mode world to "keep track" of
> "incidents" that might happen in, e.g., a factory setting? Let's say a
> piece of equipment has various things in its life that happen to it:
> breakdown, warning, maintenance, etc. that you want to keep track of in an
> org-mode way. Would it be something in the TODO/GTD realm, or something
> custom?
LB,
You can structure your file any way you like.
You might consider either:
----------------------------------------------------------------------
- Organize tickets by time, adding to the bottom, but tagging them against
machines by serial or something similar
* Tickets
** TODO Fix it again :MACHINE_X:
** DONE Eat a sock :DRYER_2:
----------------------------------------------------------------------
- Organize tickets by machine first, then time
* Tickets
** Machine X
*** TODO Fix it again
** Dryer 2
*** DONE Eat a sock
YMMV. You can do reporting on either with column views.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2020-02-27 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:55 Incident tracking Lawrence Bottorff
2020-02-27 23:28 ` Russell Adams [this message]
2020-02-28 1:00 ` Tim Cross
2020-02-28 1:50 ` Samuel Wales
2020-02-28 15:26 ` Lawrence Bottorff
2020-02-28 16:28 ` Russell Adams
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=20200227232806.GF16935@volibear \
--to=rladams@adamsinfoserv.com \
--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
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).