Reporting bugs from applications - how to configure

[Mateusz Kurleto]

I am new to atlassian products so excuse me for another newbie question. I need my customers to be able to report bugs from ou applications. I cant imagine buying a user account for each of my customers so I suppose there's a way have it happend other than giving my customers access to my JIRA.

What I am hoping to get is a "Report a bug" link in my apps so that a bug report comes into projets's bug with user description, possibly screenshot as well. How do I do that?

For my own team we have chosen Bonfire as it speeds up things a lot, but as we deploy applications for our customers we wont their users to be able to report bugs.

Another thing is - can I somehow let my customers see issues? Or do they need account in JIRA for that? What I mean is, we used trac before and there I was able to let my customers see what's happening with their issues - are they resolved, declined or what.

[Dieter · Accepted solution]

I think, the issue collector https://plugins.atlassian.com/583856 also may partly meet your requirements.

[Andy Brook [Plugin People]]

Thanks for that, I didnt know it exists, has some good ideas!

[Joe Clark]

+1 recommendation for the Issue Collector. We use this in the Confluence team.

[Christian Czaia _Decadis AG_]

Have you thought of letting your customers create issues from e-mail via the JIRA mail handler?

http://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email

[Mateusz Kurleto]

That's one possible solution. Will do OK if there aint any better:)

[Andy Brook [Plugin People]]

For point1, if you have programmatic control, email is probaly the best way to integrate (except if you are "ondemand" </sigh>) you can do some quite nifty things:

With JEMH, then you can, in the subject or body, indicate a fields in the subject such as project,component,issuetype, and custom fields. You don't need a specific per customer user as a defaultReporter can be set.

If you need to be interactive, thats interesting. You need a landing page for users to provide various bits and pieces of information and upload data. You can host your own webpage and email JEMH with the details (or even do it in Confluence, see mailform format). Having this as part of JEMH natively is also possible in the future, I've put this up as JEMH-563.

To include users in issue notifications is not straightforward if you dont create users for the company and report bugs 'on their behalf'. Potentially you could create customfield values with a nominee account, for reference, then use JETI. Depends on your exact licensing situation/need.

[Eva]

Does the customer need a unique account? is there any reason why you didnt create a general one for htem to access?