Owners as options in Quality Management reports

On 6/21/2011 7:53 AM, mbeaty wrote:

When running a report in Quality Management, I try to select an owner
to filter by and the only available option is "unassigned".
There are 11 or so users that are in the project. Does anyone know
what went wrong?

Are you running Birt of Cognos reports? Which report are you trying to
run? Which version of RQM?

Peter.

On 6/21/2011 7:53 AM, mbeaty wrote:

When running a report in Quality Management, I try to select an owner
to filter by and the only available option is "unassigned".
There are 11 or so users that are in the project. Does anyone know
what went wrong?

Are you running Birt of Cognos reports? Which report are you trying to
run? Which version of RQM?

Peter.

I am running Birt reports (I am assuming those are the ones available under the "reports" tab at the top of the RQM Quality Management page).

I am trying to run a TER List Report, but I have found this issue in every report I have tried to run so far. The odd thing is, I do not see this problem in a scratch project we were using. This leads me to think that there may be some small setting we forgot to set in the project we are having an issue with.

We are using v. 3 release candidate 2.

On 6/22/2011 12:53 PM, mbeaty wrote:

I am running Birt reports (I am assuming those are the ones available
under the "reports" tab at the top of the RQM Quality
Management page).

I am trying to run a TER List Report, but I have found this issue in
every report I have tried to run so far. The odd thing is, I do not
see this problem in a scratch project we were using. This leads me to
think that there may be some small setting we forgot to set in the
project we are having an issue with.

We are using v. 3 release candidate 2.

Hello.
If all your report parameters are empty then most likely the data
collection jobs that populate the Data Warehouse have not run.

See this online help page:
https://jazz.net/help-dev/clm/topic/com.ibm.rational.rcpr.help.doc/topics/t_running_the_data_collection_jobs.html

Btw. the final release bits are now available.

Hope this helps,
Peter Haumer.

What is the risk of this operation? If I run all the data collection operations, is there any risk of losing other information, such as test execution results? Or is this a routine procedure?

On 6/22/2011 12:53 PM, mbeaty wrote:

I am running Birt reports (I am assuming those are the ones available
under the "reports" tab at the top of the RQM Quality
Management page).

I am trying to run a TER List Report, but I have found this issue in
every report I have tried to run so far. The odd thing is, I do not
see this problem in a scratch project we were using. This leads me to
think that there may be some small setting we forgot to set in the
project we are having an issue with.

We are using v. 3 release candidate 2.

Hello.
If all your report parameters are empty then most likely the data
collection jobs that populate the Data Warehouse have not run.

See this online help page:
https://jazz.net/help-dev/clm/topic/com.ibm.rational.rcpr.help.doc/topics/t_running_the_data_collection_jobs.html

Btw. the final release bits are now available.

Hope this helps,
Peter Haumer.

Hi Matt,

The TER Listing report is not data warehouse based so running the ETL won't solve this problem. You may be encountering a change we made in 3.0.1.

In 3.0.1, the TER Owner parameter will only show users who are actually owners of TERs. So if you did not assign owners to your TERs you will only see "Unassigned" in the Owner parameter.

Previously, all the users in the system would appear in the TER Owner parameter. We had some customers using LDAP that had VERY long user lists that made the parameter unusable which prompted this change.

I think I found out the issue we were having. We only assigned test suite execution records for people to accomplish. The report did not query test suite execution records, so the field did not get populated.
Thank you for your help everybody

Hi Matt,

The TER Listing report is not data warehouse based so running the ETL won't solve this problem. You may be encountering a change we made in 3.0.1.

In 3.0.1, the TER Owner parameter will only show users who are actually owners of TERs. So if you did not assign owners to your TERs you will only see "Unassigned" in the Owner parameter.

Previously, all the users in the system would appear in the TER Owner parameter. We had some customers using LDAP that had VERY long user lists that made the parameter unusable which prompted this change.