Has anyone see an issue where users cannot see data in a cross-project JRS report?
Accepted answer
For the first user, the fact that he can see the project data because he has the JazzAdmin role does not grant the rights to see the report data in JRS. He needs to be a project member.
For the test ID, I don't think that Team membership is taken into account, try to assign it as a project member.
Best Regards,
Francesco Chiossi
Comments
Francesco,
Thanks for the response. I added the first user as a project member of project C yesterday and all of the data collection jobs have run overnight, so I will have him test it again when he gets into work today.
For the Jazzdemo user, it is a project member of project A and project C and still can see no data. He has been project members in those projects for a few days now. For project A I even assigned him the "Project Admin" role (a few days ago) which is a role that will give him all permissions across the board to rule out a role/permissions issue and that ID still cannot see any data via JRS.
Any other ideas?
I marked this as the accepted answer since it is the most likely to be a cause elsewhere. I also had the problem of not having an email address set for my test ID, so that was the cause of the other issues.
3 other answers
after you assign the other users as project members you need to rerun the ETL in order for them to have access to the project data.
If you are using the Java ETL is the common job for all applications.
If you are using DCC is the
Comments
One of my users is a JazzAdmin, so he can see all data in every project. Does he need to have specific access to the project to see data via JRS reports? He was one of the users who could see project A data, but not the other data via the JRS report, but could see all data in the regular queries/widgets.
Also, I have a test ID called Jazzdemo. That user has not been able to see any of the data, not even for project A which he has been a team member. I made Jazzdemo an admin for JRS and when I try to use that ID to create a report in JRS it cannot see any of the RTC projects; therefore, it cannot create a report at all.
All of the data collection jobs have run overnight. Any other ideas?
the project access control uses the email address as the identifier on which the permissions are looked up.
Does your test user have a valid email address in CLM?
Best Regards,
Francesco Chiossi
Comments
Interesting! No, the Jazzdemo ID does not have an email address associated with it. I will have my sys admin add a valid email address in AD. Will then sync with jazz and make sure all of my data collection jobs run again. Then will test it out.
Thanks for this info!!!
Francesco,
I had success with my first (jazzadmin) user!! He was able to log on this morning and see the project C data, so adding him to the project worked.
I am still having no luck with the Jazzdemo ID. An email address was added to it in AD and successfully synced with Jazz. I have rerun all of the data collection jobs for Jazz and CCM. I refreshed the Data Warehouse in the JRS application. I have logged out and logged back in with Jazzdemo and it still cannot see any data in the JRS widget or any projects when trying to create a new JRS report. He is a member of project A and project C. Is there anything else I need to run for this to work?
Thanks for your assistance!
you might need to check in the data warehouse if the change of email address has been picked up, if not you might need to do a full load for the JTS job.
To check the data in the data warehouse for the user, you can use a query like this:
select * from RIODS.RESOURCE where NAME='Jazzdemo';and check that there is the email populated in REFERENCE_ID.
NOTE: replace Jazzdemo with the actual user id.
Best Regards,
Francesco Chiossi
Comments
I decided to just wait for everything to run overnight and it is working this morning! Thanks for letting me know that everything is tied back to the email address and to run the Java ETL after assigning permissions to the project. Those two things fixed all the issues I was having!!
Glad to hear the issue was fixed.
Thanks for your feedback, Janet!
1 vote