[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [office] Using JIRA
Mary, am I correct in assuming from your remarks that processing on JIRA is not a substitute for a comment resolution log? - Dennis -----Original Message----- From: Mary McRae [mailto:mary.mcrae@oasis-open.org] Sent: Tuesday, May 26, 2009 09:44 To: dennis.hamilton@acm.org Cc: robert_weir@us.ibm.com; office@lists.oasis-open.org Subject: Re: [office] Using JIRA Hi Dennis, No response is required to be sent to the submitter - although it's certainly a nice idea; the issue must be noted and its resolution recorded in the comment resolution log. Regards, Mary Mary P McRae Director, Standards Development Technical Committee Administrator OASIS: Advancing open standards for the information society email: mary.mcrae@oasis-open.org web: www.oasis-open.org twitter: fiberartisan #oasisopen phone: 1.603.232.9090 Standards are like parachutes: they work best when they're open. On May 26, 2009, at 12:21 PM, Dennis E. Hamilton wrote: > Although I still think an explicit response is more powerful (since > I think > we are supposed to do that during public review anyhow?), I accept > that it > might be burdensome to do. > > I'm happy to do that much since it doesn't require JIRA privileges > to carry > out, if you're willing for it to be done on a voluntary, casual basis. > > - Dennis > > -----Original Message----- > From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] > Sent: Monday, May 25, 2009 10:22 > To: office@lists.oasis-open.org > Subject: RE: [office] Using JIRA > > "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 05/24/2009 > 12:44:52 PM: > >> >> I think your (3) is also great, but for us to do that we have to >> recall > that >> the public commenter might want to know where the JIRA issue is, so >> they > can >> see our discussion. Also, it would help in any follow-up from public >> commenters concerning what they see us making of their comment, since > they >> can't put comments directly on JIRA. > > This is easy. Since every issue ported over to JIRA has the > original URL > in the "Description" field, the original poster can simply search > for that > URL in JIRA to retrieve the current status of that issue. > > I also include the original submitters email address, so they can > easily > look up the current status of all of their issues. > >> Although it feels clumsy and will add material to the office-comment > list, I >> have the following suggestion for at least new JIRA issues that are > created >> for a submission on office-comment: (1) reply to the office- >> comment, (2) >> include the comment submitter and the office-comment list in the >> reply, > and >> (3) report that the comment has been turned into JIRA issue(s) with > their >> numbers and their URLs. (I have confirmed that the JIRA is >> available to >> public access, so this should all work.) > > This is unnecessary and would just make more work for me. See above > for > how the original submitter can look up their items on JIRA. > > We can put the information on how to search JIRA in a monthly note > to the > comment list. > > -Rob > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]