Manipulating Issue collector

Question

Right now I can play around with the issue collector for a specifik project and I can get that working fine. I am wandering if anyone has had success with generating javascript for issue collector for one project (project A), and manipulating the javascript code so issue collector can be used for different project (project B) ?

what I mean is, if I setup issue collector in project A, and export the javascript can I manipulate it and use in project B?

Or am I forced to create issue collector in each project individually? If the answer is yes, is there a multi create tool to do this? or can I create the issue collector by calling an API?

Ste Wright · Answer

No worries Simon.

Let us know what you decide!

Ste

Simon Rasmussen_u3lf4n · Answer

Thanks @Ste Wright

It seems I am probably approaching this in a wrong way. I will have to have a closer look at the page you linked to, but it looks like I will need service management as you say or a completely different setup. thanks for the help. :-)

Ste Wright · Answer

Hi @Simon Rasmussen

There is some documentation for more advanced Issue Collector functionality - for example, see this help page which might have some helpful snippets.

Unless this is being pre-built into sites though as intended - I'd consider an alternative.

For example, you could use Jira Service Management. You could consider...

* Having a Portal for customers to raise issues through
* Routing them based on user's email domain* It might be possible to have all clients in Insights Asset Management, to link requests to a specific clients' details

* Using automation to copy these to internal Projects where needed, based on data entered into the form

Let us know what you think!

Ste