<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello Rob,<div><br></div><div>As far as I'm concerned, I set the fixVersion to 4.2.x if I know I won't work on the issue before the next code freeze (currently 4.2.0.Beta3), so at least it means that I noticed it but decided not to work on it yet. I set a fix version on all the issues I plan to work on to the next version we'll release, and sometimes I even set the status to "coding in progress", so I can use JIRA filters to find the issues even faster.</div><div><br></div><div>Feel free to correct me if my method is wrong ;-)</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Best regards,</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">/Xavier<br><br><br></div></span></span>
</div>
<br><div><div>On 09 Jun 2014, at 10:11, Rob Stryker <<a href="mailto:rstryker@redhat.com">rstryker@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi All:<br><br>Do we have a document available with the proper way to triage issues? I <br>seriously have no idea anymore, and every time I try to change an old <br>issue, I end up getting an email telling me that it's not triaged now.<br><br>I used to assign myself, even if I didn't intend to work on it, to <br>indicate that it "was read". I was told this was incorrect, and that <br>there should be no assignee if nobody is actively working on it.<br><br>I also used to mark it as targeted to later, but I was told this was <br>vague and should not be used as a dumping ground for all issues that <br>aren't on the plan.<br><br>But if I leave the fix version blank (to indicate it is not on my plan), <br>I get an email telling me the issue is untriaged.<br><br>I also tried commenting on issues, to indicate that I've seen them, but <br>didn't change the fix version or assignee since I did not have a firm <br>target for it.... but this gets the same emails.<br><br>Should I go in right now and bulk-change all my unassigned untargeted <br>issues to myself with a fix version, even if I have no idea if that fix <br>version is accurate? Or should I mark all I don't have a firm target for <br>to "Later" ?<br><br>What's the process here?<br><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br></blockquote></div><br></div></body></html>