Not a big deal, but thanks for looking into it Tomaz. On Sun Dec 14 2014 at 6:43:45 AM Tomaz Muraus <to...@apache.org> wrote:
> I just had a look and it seems like projects still can't use a custom field > configuration. > > I will open INFRA ticket and ask them if it's possible to change that or if > they can create a new field configuration for our project. > > On Sat, Dec 13, 2014 at 1:55 PM, Tomaz Muraus <to...@apache.org> wrote: > > > > Hey, > > > > Yeah I've also been using labels for that. I think adding a new > (optional) > > provider / driver field is reasonable though > > > > I will have a look at adding a new field for that - last time I had a > look > > (over a year ago) it was locked and projects couldn't use custom fields, > > but this might have changed since then. > > > > On Fri, Dec 12, 2014 at 4:24 PM, Eric Johnson <erjoh...@google.com> > wrote: > >> > >> Hi all, > >> > >> I'd like to have a better way of triaging / finding Jira issues. What do > >> you think about introducing a "provider" custom field and surfacing that > >> in > >> the "New/Edit Issue" flow? > >> > >> For now and I"m trying to use "Lables", but it's not part of the > >> create/edit flow. I've bulk-edited the GCE issues and created a filter, > >> > >> project = LIBCLOUD AND resolution = Unresolved AND (labels = google OR > >> summary ~ gce OR summary ~ google) ORDER BY priority DESC > >> > >> But I don't seem to be able to make that public. > >> > >> Thanks! > >> Eric > >> > > >
