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?
Possible? Probably
The best option, given the fact Issue Collectors haven't changed much over the releases? It depends on the need.
How many Issue Collectors do you intend to create? What's the need for them?
Ste
@Ste Wright I was thinking of using issue collectors in a seperate web interface we have with our customers, so they can use the issue collector to create new issues.
There are quite a lot of projects, more than 500, each for different customers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
Let us know what you think!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries Simon.
Let us know what you decide!
Ste
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.