How do I get the URL to an issue collector?

[connie.nomann@slcc.edu]

I followed the instructions on this page:

https://confluence.atlassian.com/jirakb/how-to-access-issue-collector-form-without-embedding-it-in-a-page-826872619.html?_ga=2.154582010.311068457.1530121063-117366610.1529354464&_gac=1.190119513.1530196039.Cj0KCQjwjtLZBRDLARIsAKT6fXyd_kt5XouqumRUGiR33tS6dBbfBafuMt1x7aTY3rHYf5_TgA4pDPgaAoxLEALw_wcB

and replaced the demo collectorId with my collectorId and replaced localhost with my domain, but I get an error message that says "Oops! Looks like this form no longer exists!" I've tried this with several collectorId's with the same result.

This is the URL that results in the screenshot below:

https://dsa-projects.atlassian.net/rest/collectors/1.0/template/form/collectorId=0a80f453?os_authType=none#

[Keyana_Azari]

I'm in the same boat - I need to customize the form but i'm unable to. Can this be reported to Atlassian as a reportable bug for fix?

[Ansar Thennaden]

Year 2022, i m here for the solution and disappointed

[David Holshouser]

It's yet another issue Atlassian gets comments on frequently, but won't do anything about

We need to be able to send a simple URL to people for an issue collector. Not a dialog buried in some CSS script embedded within a web page. Just a simple URL. Why is that so hard. None of the above did anything for me.

[Ericka_Clements]

Same. Was not able to generate a URL using the steps above. And our company intranet does not allow Javascript so I'm a bit stuck. 

[gary.powell]

I'm having the same issue with the CUSTOM collector, damn!

[David Holshouser]

Years later and we still can't do links in Jira Server.

[Rachel Wright]

Hi connie.nomann@slcc.edu,

Here's the URL format I've always used:  

https://[Jira URL]/rest/collectors/1.0/template/form/[collector-ID]

I just tested it on a Cloud instance and it worked for me.

What happens when you try to visit the Issue Collector in Jira?  The URL to the collector's setting page should be in the format:

https://[Jira URL]/secure/ViewCollector!default.jspa?projectKey=[project-key]&collectorId=[collector-ID]

Does it load as expected either from a URL or from the Jira admin console?  (Visit: Project > Settings > Issue collector)

I've seen the image in your screenshot before, but it was when the form was "disabled", not "missing".

Let us know!

Rachel Wright
Author, Jira Strategy Admin Workbook

[connie.nomann@slcc.edu]

Hi Rachel,

Thank your for your replay.

I use your format and replace [Jira URL] with my coud instance of Jira and [collector-ID] with the collector ID for the issue collector I created:

https://dsa-projects.atlassian.net/rest/collectors/1.0/template/form/collectorId=cba667f8

and I still get the "Oops! Looks like this form no longer exists!"

I can view the issue collector I created when visit the control panel. Here is a screenshot of the list of collectors:

[Rachel Wright]

Hi connie.nomann@slcc.edu,

Thanks for the additional details.  What happens when you try this link?  

https://dsa-projects.atlassian.net/rest/collectors/1.0/template/form/cba667f8

It doesn't load anything for me, but it doesn't give the error either.  If that's doesn't work, here's what I'd try next:

1. Create a brand new Issue Collector, to see if maybe there's something wrong with the existing one and a new ID allows it to work.

2. Submit a bug ticket to Atlassian.

Let us know if any of the above work!

Cheers,

Rachel Wright

[connie.nomann@slcc.edu]

Hi Rachel,

There must have been something wrong  with the Issue Collector I was trying to use. I created a new one and it worked with the format you shared.

Thank you for your help. I really appreciate it.

Best,

Connie

[connie.nomann@slcc.edu]

I think there is a bug when using a custom Issue Collector. The first test I did was using one of the built in issues. The custom Issue Collector just returns an empty page.

[connie.nomann@slcc.edu]

How do I submit this bug?

[Rachel Wright]

Hi again connie.nomann@slcc.edu, you can initiate a support request from within your app.  Visit:  Admin > System > Troubleshooting and support tools.  Then click the "Get Help" tab. 

You can also visit:  support.atlassian.com to see the help options or https://support.atlassian.com/contact/ to raise an issue.

You'll need your SEN ("Support Entitlement Number") which you can obtain from Admin > Applications > Versions and licenses.

You should also send Atlassian a "Support Zip" which contains configuration options and system settings to help them troubleshoot.

Good luck and have a great day!

Rachel

[Paul Johnston]

Hi,

I found the same issue. Was this a bug? 

Thanks,

Paul

[Chris Saunders]

Very similar here, link works great for a template form but not for a custom form

Chris

[Larry Peery]

Same here. VERY frustrating to not be able to use the custom form.

[Joann Schatz]

Watching this.... really would love to be able to use the custom form. I currently have it linking to the 'Got Feedback' template, which is honestly terrible and just doesn't make sense for my purpose... Hope Atlassian fixes this soon!!!!

[Siddhartha Penakalapati]

same issue as above...

[Carey Chesmore]

Same issue as above. This was working for me at one time, and now I receive the same error as the image displays above. I'm not sure what has changed, but it no longer works.

[Javier Villanueva]

Same issue with CUSTOM template...

[Kilian Lenz]

Same issue here... As soon as I use a custom issue collector, I get a blank page.

[Artur Franczuk]

data center and tried 6 different versions of links - no one is working

[Scott Boisvert]

Similar issue. Custom form doesn't work, but the default feedback template does.

[Luana Momm]

Does anyone had success with this using the custom form?

[Olga Toverovskaya]

Hi Everyone, it's nearly 2022 and with 2018 well behind us and the world embraced in a countless evolution of COVID, this issue seems to still be unresolved.  Any workarounds identified for this yet?  

[David Holshouser]

I'm sure the switch to cloud/datacenter will make this all better.~

[Olga Toverovskaya]

I'm using an on-prem instance but this bug has basically rendered months of work learning Jira useless b/c stylistically the trigger button is a deal breaker for us.  I'll check back with admins after I'm done having a cow over this OMG