cannot add widget to RTC dashboard
2 answers
could you please expand on this, of interest would be the specific
- widget
- version of RTC
- were the project categories in RTC altered in any way
if it is the CQ Widget, here is one earlier issue that I would like to mention:
ClearQuest Widget not found when selecting CQ Application in Dashboard (177083)
which was resolved after a reboot of the CQ server and re applying of the association to cq schema repo in RTC.
- widget
- version of RTC
- were the project categories in RTC altered in any way
if it is the CQ Widget, here is one earlier issue that I would like to mention:
ClearQuest Widget not found when selecting CQ Application in Dashboard (177083)
which was resolved after a reboot of the CQ server and re applying of the association to cq schema repo in RTC.
Comments
Hi Deenesh,
The RTC version is 4.0.1. For example when I click add widget on any project areas, I am not able to see any inbuilt widgets at all(work items types, general, build and so on).
So this applied to all widgets.
I am not sure if the project categories were altered but they look to be fine.
Would you know what could be the cause?
Thanks
I do not know of any known issue for this
but I suspect the storage area keys may need to be verified.
If storage area keys stored in the DB for
Dashboard ()
differ from the keys referred to by
JTS in the Web UI
you might experience Dashboard issues.
to verify:
1. Check Consumers (Inbound) for "from
https://repo_url:403/jts/admin#action=com.ibm.team.repository.admin.configureOAuth
2. Check for the same key in DB using
repotools-jts -listStorageAreaKeys toFile="jts_keys.log"
if they do not match,
- alter the value against ""jts_keys.log" and perform a
- set the same value for "com.ibm.team.dashboard.nohistory" as well
and perform
repotools -setStorageAreaKyes fromFile="jts_keys.log"
you may additionally need to check the match for "
if this does not still help, I would suggest contacting Support.
but I suspect the storage area keys may need to be verified.
If storage area keys stored in the DB for
Dashboard ()
differ from the keys referred to by
JTS in the Web UI
you might experience Dashboard issues.
to verify:
1. Check Consumers (Inbound) for "from
https://repo_url:403/jts/admin#action=com.ibm.team.repository.admin.configureOAuth
2. Check for the same key in DB using
repotools-jts -listStorageAreaKeys toFile="jts_keys.log"
if they do not match,
- alter the value against ""jts_keys.log" and perform a
- set the same value for "com.ibm.team.dashboard.nohistory" as well
and perform
repotools -setStorageAreaKyes fromFile="jts_keys.log"
you may additionally need to check the match for "
if this does not still help, I would suggest contacting Support.