Well, my experimentation was to see how things worked in practice so we
could agree on actual use of JIRA, within its constraints, especially since
it doesn't provide the same features and view to all members.
I shall desist from touching ODF JIRA until there is an agreed process.
Meanwhile, I am reluctant to do more resolution of comments on my plate by
e-mail list (e.g., parceling out recommendations on the parts of #329 at
<http://lists.oasis-open.org/archives/office/200905/msg00005.html> in a way
where the parts for which action is recommended aren't lost and are easy to
review and discuss). Accomplishing this on JIRA, and the creation of
sub-tasks to do it, strikes me as a natural. I look forward to that
capability becoming available.
- Dennis
-----Original Message-----
From: [mailto:]
http://lists.oasis-open.org/archives/office/200905/msg00019.html
Sent: Wednesday, May 06, 2009 02:07
To:
Subject: Re: [office] office-comment -> JIRA migration
On 05/06/09 06:20, wrote:
http://lists.oasis-open.org/archives/office/200905/msg00016.html
> "Dennis E. Hamilton" <> wrote on 05/05/2009
> 11:41:00 PM:
>
> Ughhh, Probably best to just add the info as a comment for now, or ask
> Michael or I to change components, etc. You can set components and
> versions when you create an issue initially, right? But creating subtasks
> just to change the component, and then deleting the patent tasks sounds
> like trouble, especially when we use subtasks for a legitimate purpose.
> For example, when you delete the parent, what happens to the children?
Agreed. I further would recommend that we do not add any new tasks
(unless they are imported from the comment list) before we have agreed
how we actually use JIRA in practice.
[ ... ]
