Hi,
I tried to get an issue collector form set up on our jira server and let workmates access via url in order to rise new tickets from there.
Issue is that "Got feedback?" and "Raise a bug" options works nice using this link
https://jira.lendrock.com/rest/collectors/latest/template/form/514c2776?os_authType=none
Otherwise "Custom" form option displays a blank screen instead of the form.
Is this a bug? Thanks Isaac
jfyi. I recently moved to Jira to cloud and it is working as expected
Hi Anton,
Thanks for that info. I can see that you are trying to direct link to the REST URL of the collector here. This is not something that I would expect to always work. I did also come across a KB from 2016 that actually suggests using this method over in How to Access Issue Collector Form without Embedding it in a Page. So it is clear to me that this is something that other users were certainly doing in older versions of Jira. That said, it's not clear to me if that specific use case is expected to be supported here.
I'm curious if perhaps using one of the javascript triggers in the default options of creating the issue collector and then embedding that into an HTML page might be able to offer a functional solution here.
I see you already found the bug report in JRASERVER-70563. I believe that this bug report more accurately reflects the problem you are seeing here than the bug ticket I have previously linked to on this thread. I can certainly understand why you might want to direct link to a single page to collect this feedback, but I believe there is an argument to be made that perhaps this is not a bug, but rather by design. The issue collectors are expected to be called via an event. We typically expect this to happen via some jquery/javascript code we provide.
But that said, I'd watch that bug ticket in case any workaround for the use case here is found I'd expect that bug ticket to be updated to reflect this.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello!
https://jira.it4all.su/rest/collectors/latest/template/form/ba42cc1b
This link generate html code, but this code not visible in browser.
I made issue collector after update to 8.6.0
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Sorry to hear about this problem. If I understand the issue here, it's that the issue collector is not displaying correctly when you select a custom option in the 'issue collector form' section. There was a known bug about this that affected a lot of Jira 7 versions before 7.12.0. Please see the bug ticket JRASERVER-66220 for details. Does that specific bug ticket accurately describe the problem you are having here?
It looks like your Jira site is using a version such as 8.2.1. That version should contain this fix if that is the same problem. So I want to confirm the description matches your report before we go any further.
It is possible that there might be a regression in the code base that re-introduced this bug. It was not very highly reported so there have not been a large number of users affected by this so far.
Please let me know.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm thinking that perhaps the bug I have linked above is not accurate for the problem described. In researching this some more, I came across this notice about changes to jQuery starting in Jira 8.0 in https://confluence.atlassian.com/jiracore/jquery-upgrade-975041040.html
It appears that this change could have the affect of breaking issue collectors created before on previous versions as the code generated to display them would be incorrect in Jira 8 and higher versions. I'm not sure if that fits the description of the problem you are having here, but I would be interested to learn if perhaps this problem began after an upgrade.
If that doesn't help, could you let me know more about the problem you are seeing? Perhaps a screenshot that highlights the problem, or other steps we could take to try to reproduce the problem would be helpful here.
Cheers,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.