Bob Morley wrote: > I am creating this from the discussion as part of ticket OFBIZ-3630. > > My issue as a non-contributor was that there is no way to distinguish > tickets that are created vs. ones that a fix as been proposed and attached. > This was important for me because it provided me a way to see which of my > tickets I have provided a patch for (and which I had just reported) as well > as being able to search through tickets that I could "provide a helping hand > on" -- each I clicked on actually already had a patch and were just sitting > as unresolved. It seemed to me it also would provide a way for contributors > to see which tickets have pending review / commit patches available vs. > reported problems. > > I had proposed the use of the Resolved status for when a fix has been > proposed and attached. This was under the influence from the "Contributors > Best Practices" guide which suggested that bugs were immediately moved to > Closed (and Resolved was not being used). > > From my understanding, the standard filters used by Contributors would cause > this issues to not come up on their radar. If using Resolved in this way is > not a reasonable solution, does anyone have a better solution? The easiest > issue I can point to is OFBIZ-3100 > (https://issues.apache.org/jira/browse/OFBIZ-3100) which has a big > collection of sub-tasks, some of which are closed, reopened, resolved, and > unresolved.
Do a search for the reporter==you, and status==patch available, or some other status.
