From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-jira.el... and Org conventions (Bastien, Carsten and all)
Date: Tue, 03 Jan 2012 09:07:49 +0100 [thread overview]
Message-ID: <80ipkt6wfe.fsf@somewhere.org> (raw)
In-Reply-To: 86hb0ez4qr.fsf@gmail.com
Hi Bao,
"Bao Haojun" wrote:
> I have implemented org-jira.el, bringing org-mode and Jira system
> together.
>
> Wrote a Wiki page for it on emacswiki:
> http://www.emacswiki.org/emacs/OrgJiraMode
>
> Hope somebody find it useful, if he/she is also using Jira and loves
> org-mode.
I had never heard of Jira, but your work definitely looks very promising.
IMHO, it should be compared with org-x and its extension to Redmine, among
others.
But this triggers, for me, another "concern" which is the very wide variety of
ways to define the same thing.
Let's just take how we represent who's gonna be assigned a task:
- In most examples we see on the Net (or in the Org manual), people use tags
with person names (or abbreviations).
- In your case, you mirror what's done in Jira (I guess) and you introduce a
property "Assignee".
- In Org issues (http://orgmode.org/worg/org-issues.html), some tasks are
given a property "Who" to indicate who has to work on them.
- In tasks used for interacting with TaskJuggler, one uses a "Resource-Id"
property.
- Still another approach is used by Juan Reyero in his advertised "Org-mode
tricks for team management" (see [1]), using a combination of TODO todo
keywords for his own tasks, and TASK keywords for tasks assigned to members
of his team.
All of this makes it hard to have one independent Org file, and be able to
cooperate with external tools (like Jira, Redmine, TaskJuggler and others) on
a "on demand" approach.
You want a Gantt chart? You need to add (or rename) "Resource-Id" properties.
Now, you would like a Web-based Bug Tracking system? Too bad: you need to add
(or rename) properties "Assignee" or ...
So, my point is: wouldn't it be better if we proposed standard properties in
Org (in the manual), and implemented mappings in the Org "integration"
packages (org-jira, org-taskjuggler, org-redmine and the like)?
So, say for example that, from now on, it's more standard in Org to use
"Assignee" (or anything else) for representing who's assigned a task, and have
every package map the property "Assignee" to whatever keyword used in external
tools for representing that concept?
If we do such,
- we _do not impose anything_ (everybody is still free to represent this task
the way he wants, be it properties or tags)
- we ensure an easy transition to use any external tool for those that used
the "to be defined" standard properties.
Best regards,
Seb
Footnotes:
[1] http://juanreyero.com/article/emacs/org-teams.html
--
Sebastien Vauban
next prev parent reply other threads:[~2012-01-03 8:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 12:08 org-jira.el Bao Haojun
2012-01-03 8:07 ` Sebastien Vauban [this message]
2012-01-03 15:53 ` org-jira.el... and Org conventions (Bastien, Carsten and all) Bao Haojun
2012-01-03 16:25 ` Sebastien Vauban
2012-01-03 16:28 ` Allen S. Rout
2012-01-04 16:47 ` Bastien
2012-01-04 17:13 ` Nick Dokos
2012-01-03 23:34 ` Standard property proposal (was: org-jira.el... and Org conventions (Bastien, Carsten and all)) Karl Voit
2012-01-04 16:50 ` Standard property proposal Bastien
2012-01-03 13:49 ` org-jira.el Marc Spitzer
2012-01-04 16:52 ` org-jira.el Bastien
2012-01-04 17:53 ` org-jira.el Nick Dokos
2012-01-05 10:00 ` org-jira.el Bastien
2012-01-05 14:42 ` org-jira.el Bao Haojun
2012-01-05 17:08 ` org-jira.el Jonathan Arkell
2012-01-06 0:32 ` org-jira.el Bao Haojun
2012-01-06 15:24 ` org-jira.el Bao Haojun
2012-01-04 18:36 ` org-jira.el Richard Riley
2012-01-04 19:49 ` org-jira.el Mehul Sanghvi
2012-01-05 10:01 ` org-jira.el Bastien
2012-01-05 15:42 ` org-jira.el OSiUX
2012-01-06 0:28 ` org-jira.el Bao Haojun
2012-01-06 15:54 ` org-jira.el Bao Haojun
2012-01-09 20:26 ` org-jira.el OSiUX
2012-01-10 2:40 ` org-jira.el Bao Haojun
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=80ipkt6wfe.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).