Tony, I agree with Terry Hynd's response and would like to provide some insight. It can be confusing that issues that exist within a project are converted to a project. I think term "Convert" is what causes some confusion. In most cases, issues aren't converted to projects, when instead, issue data is copied to a project (name, description, custom data, updates, documents, etc.) and a resolving object link exists between the original issue and the resolving project. Understanding this relationship is absolutely critical for you if you are starting with requests and then converting to projects. With this understanding, you're able to create issue based reports where you pull in or filter by resolving project details, which is really powerful. For your use case, here's what I recommend> In an issue report, you can use these filters as a starting point: Issue>>Resolve Project ID>>Is Not Blank (this ensures you're only getting issues that have been converted to a project) Issue >>Entered By ID>>Person (this pulls all issues entered by the person you're interested in) Now in the view, you can pull in any of the resolving project details you want: Issue>>Resolve Project>>Owner Name (show the owner of the resolving project) Issue>>Resolve Project>>Entered by ID (show the ID of the person who entered the project) In this model, you can actually make an issue report look like a project report because all you're pulling in are resolving project details. I prefer this type of reporting, especially in a "demand management" environment where everything begins as a request.
