Support
To check known issues (or if you want to file one), view this app's issue tracker.
To learn more about the app, you should:
- Look around the forums.
This is a supported app, so you may contact the vendor (or support contact) for help:
Website: http://www.atlassian.com
Support System: http://support.atlassian.com
San Francisco: +1 415 701 1110
Sydney: +61 2 9262 1443
Amsterdam: +31 20 796 0060
Description
The Jira Issue Collector is now bundled with Jira 5.1! All Jira releases after Jira 5.1 will automatically include a compatible version.
Need to capture feedback on your website or web application? Want to make it easy for end users to directly create bugs so your developers can act on them?
The Jira Issue Collector plugin makes collecting feedback and bugs from your users and customers easier than ever.
If you develop web-applications or web sites, the Jira Issue Collector is the best way to turn your customers' and users' feedback and problems directly into Jira issues, all without requiring a Jira login.
Instead of having to navigate to Jira to raise bugs users will be able to raise issues directly from within your web-application, in a feedback form that you design!
Users will see a button (or "trigger") for feedback, and can click the button to raise feedback or bugs on a form embedded in your web application.
To create an Issue Collector, simply:
- Configure an Issue Collector for a Jira Project
- Customize the Issue Collector with the headings, format, and Jira fields that you want displayed
- Jira generates a single line of javascript for embedding the Issue Collector
- Embed the single line of javascript in the page where you want the feedback button to appear.
Version history
1.4.7Jira Server 6.2 - 6.2.72014-03-066.2 compatibility No release notes.1.2.5Jira Server 5.0 - 5.2.112012-09-17Fixed custom trigger bug Fixed one issue affecting custom triggers in the Issue Collector.
This issue occurred when a custom collector which supplied the javascript code in the Issue Collector form also extended the Issue Collector ATL_JQ_PAGE_PROPS in javascript .
(Note the use of code supplied in the Issue Collector is deprecated)
1.2.4Jira Server 5.0 - 5.1.32012-08-17Fixed attachment bug No release notes.1.2.2Jira Server 5.0 - 5.1.22012-08-07Edit and Copy Issue Collectors with base URL fix Major features
- Editing and copying of issue collectors is now supported
- Custom trigger functions should now be embedded in target page, not specified in collector configuration. Existing trigger functions in configuration are still supported, but new collectors need to have them defined in the target page source (see Advanced Use of the Issue Collector)
- JavaScript can be used to define values for fields not displayed in the Custom Collector form
Bugfixes:
- Prevents JavaScript code that may download resources and open feedback form from different URL than the one it is downloaded from.
- Jira Global Administrators now have permission for viewing and creating issue collectors (not just creating)
- Trigger is no longer displayed on the embeded page if the issue collector is disabled or invalid
- Improved handling when a Jira field is required when creating an issue collector
- Fixed an issue with setting default values for fields using JavaScript
- Fixed an issue where the wrong field would have the initial focus in the issue collector form
Upgrading from the 1.1 version
- Since some information such as the trigger style used to be cached by the browsers, it is recommended to update any web pages pages with new issue collector urls the first time you edit. Skipping this may cause users to not see changes to issue collectors edited in the future.
- Trigger functions in Collector Configuration are deprecated due to security reasons and support for them will be removed in the future. Move any JavaScript used for existing Custom triggers to the production pages instead of specifying them in the issue collector configuration.
- JavaScript can be used to set field values for fields not visible on the issue collector form. While this adds more flexibility to the issue collector, make sure that any fields on your issue would not cause a problem if set by anonymous users.
1.1.1Jira Server 5.0 - 5.1.22012-07-29Bug fixes from version 1.1 - Fixes an issue where the Issue Collector fails if the context path ends in s
- Fixes an issue where Jira Administrators don't have access to View an Issue Collector
1.1Jira Server 5.0 - 5.12012-07-10Now supported and bundled with Jira 5.1 The Jira Issue Collector is now supported by Atlassian!
The Jira issue Collector is bundled in Jira 5.1, so you no longer need to install the Issue Collector plugin, but can also be used with Jira 5.0.
The Jira Issue Collector is also available in Jira OnDemand.
1.0.23-betaJira Server 4.4 - 5.0.72012-03-20Moved to the atlassian bitbucket repo No release notes.1.0.22-betaJira Server 4.4 - 5.0.72012-02-28Minor feature improvements Version 1.0.22-beta • Released 2012-02-28 • No Vendor Support • Paid via Vendor • Atlassian Closed-Source* Ben Speakmon added the ability to set default field values
* Some minor bug fixes
1.0.20-betaJira Server 4.4 - 5.0.72012-02-15Fixed some issues with collecting additional properties Version 1.0.20-beta • Released 2012-02-15 • No Vendor Support • Paid via Vendor • Atlassian Closed-SourceNo release notes.1.0.19-betaJira Server 4.4 - 5.0.72012-02-14Added spinner while form is loading Version 1.0.19-beta • Released 2012-02-14 • No Vendor Support • Paid via Vendor • Atlassian Closed-SourceNo release notes.1.0.18-betaJira Server 4.4 - 5.0.72012-02-13Custom messages and global admin Version 1.0.18-beta • Released 2012-02-13 • No Vendor Support • Paid via Vendor • Atlassian Closed-SourceThis release adds two new features:
- Custom messages at the top of a collector (using wiki markup)
- A global admin section to make it easier to find issue collectors using the gg shortcut
1.0.16-betaJira Server 4.4 - 5.0.72012-02-06Minor bugfixes Version 1.0.16-beta • Released 2012-02-06 • No Vendor Support • Paid via Vendor • Atlassian Closed-SourceAdded support for adding additional environment properties either via an object or callback. The object/callback needs to be defined as a global var under ATL_JQ.feedbackProperties.
For example:
<script>
var ATL_JQ = {
feedbackProperties: {
"foo": "bar"
}
}
</script>
1.0.15-betaJira Server 4.4 - 5.0.72012-02-06Bugfixes Version 1.0.15-beta • Released 2012-02-06 • No Vendor Support • Paid via Vendor • Atlassian Closed-SourceNo release notes.1.0.14-betaJira Server 4.4 - 5.0.72012-01-29Minor bugfixes Version 1.0.14-beta • Released 2012-01-29 • No Vendor Support • Paid via Vendor • Atlassian Closed-SourceNo release notes.1.0.11-betaJira Server 4.4 - 5.0.72012-01-02Minor bug fix Version 1.0.11-beta • Released 2012-01-02 • No Vendor Support • Free • Apache License, Version 2.0 (ASL)No release notes.1.0.8-betaJira Server 4.4 - 5.0.72011-12-15Lots of bug fixes Version 1.0.8-beta • Released 2011-12-15 • No Vendor Support • Free • Apache License, Version 2.0 (ASL)- Fixed a number of typos
- Permission problems when creating labels
- Reintroduced the right hand trigger (now called 'Vertical')
1.0.7-betaJira Server 4.4 - 5.0.72011-12-11Added custom templates and lots of other improvements Version 1.0.7-beta • Released 2011-12-11 • No Vendor Support • Free • Apache License, Version 2.0 (ASL)This release represents a major overhaul of the issue collector.
What's new?
- Project admin UI for issue collecotrs
- Custom form templates!
- jQuery on the client side
- Improved trigger styles
- Better error handling
- Matching reporters by e-mail address
- And lots of bug fixes!
1.0.0-beta9Jira Server 4.4.3 - 5.0.72011-11-01Bugfixes Version 1.0.0-beta9 • Released 2011-11-01 • No Vendor Support • Free • Lesser GNU General Public License (LGPL)No release notes.1.0.0-beta5Jira Server 4.3 - 4.4.52011-09-20Inital beta release Version 1.0.0-beta5 • Released 2011-09-20 • No Vendor Support • Free • Lesser GNU General Public License (LGPL)No release notes.