On Fri, May 31, 2019 at 3:21 AM Antoine Pitrou <anto...@python.org> wrote: > > > Le 31/05/2019 à 10:04, Fan Liya a écrit : > > @Antoine Pitrou, you mean the titles of JIRA/PR should be chosen carefully? > > That helps a bit for visual filtering, but visual filtering quickly > becomes inefficient if there are too many issues. > > No, I mean having views that only display certain kinds of issues (for > example I'm interested in C++ and Python issues, not so much the other > kinds). > > We also currently don't record any interesting information wrt. > priority. So if you take a look at the "Issues to do" list for 0.14.0, > for example, you get an (unordered?) list of 252 issues, which is > *truncated* by the stupid JIRA software: > https://issues.apache.org/jira/projects/ARROW/versions/12344925 > > ... and when you click on "View in Issue Navigator" to get the > untruncated list, you get an unhelpful text box with a SQL-query and no > easy way to refine your search. Not to mention the annoying pagination > with tiny links at the bottom middle-left, and the general UI slowness. >
That is annoying. I always start from the unfiltered Basic issue view with Project = ARROW Components = C++, Python (maybe with Fix Version = 0.14.0) You can then click "Save As" in the dropdown toward the top of the page and save this search so you can navigate to it easily next time. > Regards > > Antoine.
