Genius. I love it. This will save me so much clicking time. Kenn
On Wed, Feb 27, 2019 at 5:20 PM Udi Meiri <eh...@google.com> wrote: > My favorite way to navigate JIRA is using a Chrome search engine. > You configure it like this: > [image: Screenshot from 2019-02-27 17-11-26.png] > (URL is: > https://issues.apache.org/jira/secure/QuickSearch.jspa?searchString=%s) > > And search by writing in the location bar: > "j BEAM-1234" will take you to that specific issue > "j beam unresolved udim" will show all unresolved issues assigned to udim > > > On Tue, Feb 26, 2019 at 9:22 PM Ahmet Altay <al...@google.com> wrote: > >> Thank you Daniel, this is great information. >> >> On Fri, Feb 22, 2019 at 11:47 AM Daniel Oliveira <danolive...@google.com> >> wrote: >> >>> Hi everyone, >>> >>> In a recent thread in this list I mentioned that it might be nice to >>> have a short guide for our Jira on the wiki since there were some aspects >>> of Jira that I found a bit unintuitive or not discover-able when I was >>> getting into the project. I went ahead and wrote one up and would >>> appreciate some feedback, especially from any contributors that may be new >>> to Beam and/or Jira. >>> >>> >>> https://cwiki.apache.org/confluence/display/BEAM/Beam+Jira+Beginner%27s+Guide >>> >>> The main two aspects that I want to make sure I got right are: >>> >>> 1. Covering details that are often confusing for new contributors, such >>> as ways Beam uses Jira that might be unique, or just unintuitive features. >>> >>> 2. Keeping it very brief and duplicating as little documentation as >>> possible. I don't want this to get outdated, so I'd much rather link to a >>> source of truth when possible. >>> >>> If anyone has any details I missed that they'd like to add, or feel that >>> they could edit the guide a bit to keep it brief and cut out unnecessary >>> info, please go ahead. Also, I'm hoping that this guide could be linked >>> from the Contribution Guide <https://beam.apache.org/contribute/> on >>> the website if people find it useful, so feedback on that front would be >>> great too. >>> >>
