OASIS Open Document Format for Office Applications (OpenDocument) TC

Why are JIRA issues cloned rather than just retargetted? Cloning will split the comments over the differnet issues and make it more confusing to talk about them. If the issue was resolved with a target, then cycling them through Resolved->Applied->Closed->Open will open them and allow a new target and resolution to be set. For example now we have two open issues 3312 and 3680 for exactly the same issue. The clone 3680 is not needed. Andreas This is a digitally signed message part

"Andreas J. Guelzow" <andreas.guelzow@concordia.ab.ca> wrote on 04/25/2011 04:19:05 PM: > Why are JIRA issues cloned rather than just retargetted? Cloning will > split the comments over the differnet issues and make it more confusing > to talk about them. > > If the issue was resolved with a target, then cycling them through > Resolved->Applied->Closed->Open will open them and allow a new target > and resolution to be set. > > For example now we have two open issues 3312 and 3680 for exactly the > same issue. The clone 3680 is not needed. > In most cases it will be sufficient to simply re-target the issue by setting a new "affects version". I can imagine some less common situations where an issue is partially addressed in ODF 1.2 with completion in ODF-Next, but that is better handled via sub issues, to preserve the connection. In any case, I think the recommendation for ODF-Next issues was, that if someone was interested in owning a particular issue, they should assign it to themselves and set Affects Version to ODF 1.2 and Fix Version to one of the ODF 1.3 CSD's. For issues that do not have owners, we can let them sit for now. -Rob

The reason I cloned that particular one (and maybe others, I forget right now), is that a resolution was set and I didn't want to simply erase it (plus I didn't know how). I have never tried the procedure Andreas suggests, and I think I had already clones the one of interest by then. Not sure. In any case, there is a lot of commentary that may not be so important and it would be useful to have a fresh sheet as well as a link back to the old stuff. If there is a different agreement, I will honor that. - Dennis
Original Message----- From: robert_weir@us.ibm.com [ mailto:robert_weir@us.ibm.com ] Sent: Monday, April 25, 2011 13:52 To: office@lists.oasis-open.org Subject: Re: [office] Unnecessary cloning of JIRA issues "Andreas J. Guelzow" <andreas.guelzow@concordia.ab.ca> wrote on 04/25/2011 04:19:05 PM: > Why are JIRA issues cloned rather than just retargetted? Cloning will > split the comments over the differnet issues and make it more confusing > to talk about them. > > If the issue was resolved with a target, then cycling them through > Resolved->Applied->Closed->Open will open them and allow a new target > and resolution to be set. > > For example now we have two open issues 3312 and 3680 for exactly the > same issue. The clone 3680 is not needed. > In most cases it will be sufficient to simply re-target the issue by setting a new "affects version". I can imagine some less common situations where an issue is partially addressed in ODF 1.2 with completion in ODF-Next, but that is better handled via sub issues, to preserve the connection. In any case, I think the recommendation for ODF-Next issues was, that if someone was interested in owning a particular issue, they should assign it to themselves and set Affects Version to ODF 1.2 and Fix Version to one of the ODF 1.3 CSD's. For issues that do not have owners, we can let them sit for now. -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