List of reporters remains (almost) empty when trying to create a JIRA defect
Hi guys,
After the installation and configuration of the OSLC plugin between my Collaborative Lifecycle Management (4.0.3) and Jira (5.2.17) I tried creating a Jira defect in QM. However, even though I can select an Assignee (which is the Jira user I logged in with) the list of Reporters only has the sublist-titles 'Suggestions' and 'All users' in it. Because of that I can not select a reporter to create a defect. So I guess that for some reason my userlist is not loaded. Anyone else who has experienced this problem or has an idea what a solution could be?
(The summary also is noted to have an error, even though some text is added in it, so that would be a second issue)
Thanks,
Kristof
2 answers
This is a known issue, please ask your system administrator to make a change in the Jira server to workaround the issue:
http://pic.dhe.ibm.com/infocenter/rliahelp/v1r1/index.jsp?topic=%2Fcom.ibm.rational.rlia.jira.doc%2Ftopics%2Fc_JIRA_troubleshoot_issue5x.html
If you cannot contact your admin, I can suggest you to use Chrome, this browser does not present this problem, even if it is not listed as a supported browser, it has worked pretty well for me.
Regards.
Comments
This unfortunately does not fix it. I already tried out the fix yesterday, using chrome doesnt do the trick either. The difference with the scenario described in the fix is that in my case when clicking on the reporter selection box I do get 'suggestions' and 'all users' in it.
When I add an issue in JIRA itself, it all works like expected too...
When I load the page in chrome, I also get a bunch of warnings/errors regarding mixed content.
It has worked for me all the times I have used Chrome. What is your Chrome version? What is your OS? Would it be possible to apply the workaround for the Jira server?
Regarding Chrome, the latest version of it (downloaded yesterday 30.0.1599.69 m on windows xp SP3) seems to block mixed content, i.e. files coming from the JIRA server which comes over HTTP when the Jazz server serves its files over https. I have been able to solve my problem now though, by downloading a newer version of the 1.1 plugin.