Searching for risks/issues for a Project Lead

[simone.croft]

Hi Jira colleagues, 

I am relatively new to Jira and would like to run some searches on issues/risks across my team. While there are 16 team members and many many more projects that sit in my team, all projects have been set up by one person (Project Lead). I was hoping to be able to search, for example, for all risks logged under all projects set up by that person so that, the search would be simpler and more error free than entering every person individually, but I can't seem to be able to do it. I suspect it is not possible, but wondered if anyone knew of a workaround? 

Many thanks in advance,

Simone

[Pete Singleton · Accepted solution]

No, you cannot query by Project Lead unfortunately.  However, you could get a list of the project keys from the admin section, based on the Project Lead, and then query across all projects, e.g.

Project IN (Proj1, Proj2, Proj3) 

[simone.croft]

Thanks for this Pete. 

This seems like quite a painful solution given the fact that many of our projects are small/short lived (we develop data, rather than software products) so I fear there is the potential to miss things out. It will be easier to list every team member and this way all projects should be covered. 

Do you know if there is a way to flag people as being in the same team so that I can just search under the team name rather than listing each individual person? 

Simone 

[Pete Singleton]

Hi Simone,

No, I do not know of a way to filter issues based on teams.

However, I would suggest that you re-think the way you manage projects in your instance if you have often creating new ones and many of them are short lived.  You should look at using a single, longer term project, and then break the work down within it based on Releases ("versions"), or Components.  This would save you all the overhead of creating new projects each time, and you can easily filter out all the completed work based on the Release (or Component).  You also get some useful functionality with Releases, such as the Release Roadmap gadget, Release Notes, etc.

[simone.croft]

Thanks Pete. 

The projects are set up in this way due to the way we bill our clients, so I don't believe we can change this set up, nor can we change the nature of the work. Data products are in essence different to software products as they are shorter and are less likely to have versions. We have only recently transitioned to Jira, so I'm hoping some ways of making life simpler will emerge, but this was one way that would certainly have done that had the functionality been available. 

Simone

[Pete Singleton]

The only reason to have separate projects is if there are differences in issue types used, workflows, screens, or significantly different user permissions.  If all these projects are alike in most ways, why keep them separate?  Using versions is just a good way to separate work as "mini projects", with a defined start and end date.  You can view by version which work is complete or still to do, and 'close' a version off when it's all done.  Ignore the terminology of 'version' or 'release', you can still use it to segregate work.