Why not create a category. Its no problem to add multiple categories to an
issue and the filters already exist
On 9 Oct 2014 21:53, "javier gomez" notifications@github.com wrote:

Hi all,

The next week on the 17th we will have the next Pizza Bugs and Fun:
http://developer.joomla.org/pbf.html

For that occasion we have created the label "PBF14" in Github:
https://github.com/joomla/joomla-cms/labels/PBF14. The idea is to create
under that label a short list of Joomla CMS issues that we would like to
see solved by the people who will participate in the PBF'14.

This label can be seen already in issues.joomla.org witch is great:

[image: screen shot 2014-10-09 at 22 52 16]
https://cloud.githubusercontent.com/assets/1375475/4583877/e111ba2c-4ff5-11e4-8c9a-fc9ee0cd923d.png

However, right now we are not able to filter by this label. Would it be
feasible to create a filter for labels in issues.joomla.org on time for
the PBF?

thanks very much ^_^

—
Reply to this email directly or view it on GitHub
#523.

A category wouldn't work for github. There's no automated integration between the two.

In theory, this should be an easy solution since we already have all the data. I might be able to tackle it this weekend if nobody else beats me to it.

Why should that matter Nick we want people to use i.j.o as the point of
truth.
On 9 Oct 2014 22:21, "Michael Babker" notifications@github.com wrote:

In theory, this should be an easy solution since we already have all the
data. I might be able to tackle it this weekend if nobody else beats me to
it.

—
Reply to this email directly or view it on GitHub
#523 (comment).

I'd like people to use whatever they'd like, that way they're more likely to contribute. For example, github has notifications in its web UI, as well as email notifications (which you used to reply to this issue). That lowers the barrier to contribution.

In short, I'd lean toward issues.joomla.org, but I'd like to make it so that people can contribute from any venue that's convenient for them.

@brianteeman - There are a couple of things we can filter on using labels that can't be filtered against otherwise, either through GitHub's native search or the tools we have available today in this app. For example, we can't filter on target branch for a PR, so searching on those labels is rather convenient if you're searching solely for 2.5 related pull requests.

I know but for the purpose of a PBF we should really be using our own tools
or there was little point in creating them
On 9 Oct 2014 22:46, "Michael Babker" notifications@github.com wrote:

@brianteeman https://github.com/brianteeman - There are a couple of
things we can filter on using labels that can't be filtered against
otherwise, either through GitHub's native search or the tools we have
available today in this app. For example, we can't filter on target branch
for a PR, so searching on those labels is rather convenient if you're
searching solely for 2.5 related pull requests, for example.

—
Reply to this email directly or view it on GitHub
#523 (comment).

For this particular case, I see it as integrating a GitHub feature into our app to give folks less reason to not use it.

Cool, I'm focusing all the documentation for PBF on JIssues and com_patchtester

Would it be possible to pass the label and other filter parameters via get too? so I could send a link like:

http://issues.joomla.org/?filter-label=PFB14

Because everything is referenced by ID with the label filter, the best I can give you is http://issues.joomla.org/?label=38 which is the ID corresponding to the PBF14 label. We don't have processing on labels to create URL friendly aliases for this type of use case but could be something we do later on if it was desired.

htaccess rule?

On 14 October 2014 13:25, Michael Babker notifications@github.com wrote:

Because everything is referenced by ID with the label filter, the best I
can give you is http://issues.joomla.org/?label=38 which is the ID
corresponding to the PBF14 label. We don't have processing on labels to
create URL friendly aliases for this type of use case but could be
something we do later on if it was desired.

—
Reply to this email directly or view it on GitHub
#523 (comment).

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

Categories have URL friendly aliases in the database to map to, and the filter states allow you to filter with those aliases or the category ID in theory. http://issues.joomla.org/?category=postgres and http://issues.joomla.org/?category=2 should return the same data set, but it looks like there's a bug in that if conditional.

Even with an htaccess rule, we just don't have code right now to lookup single labels by any reference value. With a new database column and model class with a couple of simple methods to lookup by the passed in value, it's good to go.

Maybe a "Permalink" button that contains the currently selected filter(s)?

http://issues.joomla.org/?label=38 works for me :) Thanks!