More screenshots are available on the examples page!
Details
Installation
Note
Please install the correct plugin for your version of JIRA!
Synchronization to JIRA is not supported in JIRA 3.7-3.10
Upgrading
When upgrading from a previous version of this plugin, we strongly recommend verifying its behaviour in a QA environment, and taking a backup of your JIRA system before deployment (as with any new plugin).
This documentation is incomplete. You need to rename the extension of the download to .jar in order for it to work. Also, there is no information on the necessary steps needed to have the salesforce information show up in a JIRA issue.
Thanks for the feedaback - We'll add a note about downloading in IE and renaming zip's to jar's. I've also updated Salesforce.com JIRA Plugin Configuration to point to how you setup JIRA to use the Custom Field types - let us know if you need more information and thanks again for taking the time to help us improve.
I installed the plug-in today and created two custom fields - a multiple cases and a multiple accounts select field. The cases field seems to work fine but I get an error when viewing the accounts field. Although, editing the field (including selecting an account) worked.
2007-11-29 07:02:28,806 TP-Processor11 ERROR [crm.salesforce.manager.SFManager] INVALID_FIELD:
select Name, Type from Account where Id='xxxxx'
^
ERROR at Row:1:Column:14
No such column 'Type' on entity 'Account'. If you are attempting to use a custom field, be sure to append
the '__c' after the custom field name. Please reference your
WSDL or the describe call for the appropriate names.
2007-11-29 07:02:28,837 TP-Processor11 ERROR [plugins.crm.jira.CRMMultiSelectCustomFieldSearcher]
Error while indexing CRM custom field
java.lang.Exception: ( Customware-CRM-plugin ) - Error message from Salesforce.com : null
at net.customware.plugins.crm.salesforce.manager.SFManager.getDisplayName(SFManager.java:236)
at net.customware.plugins.crm.jira.CRMMultiSelectCustomFieldSearcher.index(CRMMultiSelectCustom
FieldSearcher.java:72)
at com.atlassian.jira.issue.index.indexers.impl.DefaultCustomFieldIndexer.addIndex(DefaultCustom
FieldIndexer.java:54)
at com.atlassian.jira.issue.index.IssueDocument.getDocument(IssueDocument.java:34)
at com.atlassian.jira.issue.index.IssueDocumentBuilderImpl.get(IssueDocumentBuilderImpl.java:14)
The error message I get an the view issue page is:
This particular function is dependent on querying Salesforce for both the name of the account and the type. You may find you need to add the type field within your Accounts page layout within Salesforce, to utilize this function properly.
However, version 1.3.3 of this plug-in has a fix for this, and is no longer dependent on the Type field in Accounts for this function. Please replace your current jar with this version and restart your JIRA instance. You should then be able to view your accounts correctly.
If you require further assistance please feel free to email CustomWare Support
We've downloaded and configures the Salesforce.com JIRA plugin. It works well. My question is why none of the Salesforce.com custom fields show up as available options in the JIRA Charting Plugin (http://confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin). All our other custom fields show up in that plugin and work well.
We're trying to create a report showing all our JIRA issues that are attached to a Salesforce.com account, and maybe another report that shows the accounts with the most JIRA issues. I was hoping to use the JIRA charting plugin for this purpose but that's not working. Ideas?
Unfortunately, the particular type of custom field searcher that our plugin inherits is not of the same type the charting plugin relies on, which is why you cannot select the account custom field to be reported on. However, you can setup a filter and generate reports based on the Salesforce.com account you require, and generate one of the default charting reports based on this filter, filtering by that particular account.
I will raise a feature request on your behalf on the Atlassian Developer Network JIRA, so be sure to check back on our future releases that could implement this feature.
I have been evaluating your salesforce/jira plugin. While everything was easily set up through this document you have provided, I still have a question or two that will hopefully get answered quickly.
One of the biggest question is whether or not there is a create jira function for all the salesforce entities rather than just for the Cases. There is at least one other Salesforce entity where we would like to use it. I have tried to use the existing ".../CreateIssueFromSFCase!default.jspa?caseId={!Case.Id}" and replacing {!Case.Id}} with {!Opportunity.Id}, but as expected that did not work. Also, it appears that it references a variable called caseId, are there other variables to handle the issue illustrated here? Or perhaps there's another jspa?
If it's not possible, what would it take to have it implemented?
Please email me if you would like to start a thread about this.
Open
This documentation is incomplete. You need to rename the extension of the download to .jar in order for it to work. Also, there is no information on the necessary steps needed to have the salesforce information show up in a JIRA issue.
Hi Evan,
Thanks for the feedaback - We'll add a note about downloading in IE and renaming zip's to jar's. I've also updated Salesforce.com JIRA Plugin Configuration to point to how you setup JIRA to use the Custom Field types - let us know if you need more information and thanks again for taking the time to help us improve.
regards,
-Rob
Updated by Jonathan Appel
Mar 07, 2008 22:57
I installed the plug-in today and created two custom fields - a multiple cases and a multiple accounts select field. The cases field seems to work fine but I get an error when viewing the accounts field. Although, editing the field (including selecting an account) worked.
2007-11-29 07:02:28,806 TP-Processor11 ERROR [crm.salesforce.manager.SFManager] INVALID_FIELD: select Name, Type from Account where Id='xxxxx' ^ ERROR at Row:1:Column:14 No such column 'Type' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names. 2007-11-29 07:02:28,837 TP-Processor11 ERROR [plugins.crm.jira.CRMMultiSelectCustomFieldSearcher] Error while indexing CRM custom field java.lang.Exception: ( Customware-CRM-plugin ) - Error message from Salesforce.com : null at net.customware.plugins.crm.salesforce.manager.SFManager.getDisplayName(SFManager.java:236) at net.customware.plugins.crm.jira.CRMMultiSelectCustomFieldSearcher.index(CRMMultiSelectCustom FieldSearcher.java:72) at com.atlassian.jira.issue.index.indexers.impl.DefaultCustomFieldIndexer.addIndex(DefaultCustom FieldIndexer.java:54) at com.atlassian.jira.issue.index.IssueDocument.getDocument(IssueDocument.java:34) at com.atlassian.jira.issue.index.IssueDocumentBuilderImpl.get(IssueDocumentBuilderImpl.java:14)The error message I get an the view issue page is:
Updated by Dominic Lovell [CustomWare]
Nov 30, 2007 12:13
Hi Gunnar,
This particular function is dependent on querying Salesforce for both the name of the account and the type. You may find you need to add the type field within your Accounts page layout within Salesforce, to utilize this function properly.
However, version 1.3.3 of this plug-in has a fix for this, and is no longer dependent on the Type field in Accounts for this function. Please replace your current jar with this version and restart your JIRA instance. You should then be able to view your accounts correctly.
If you require further assistance please feel free to email CustomWare Support
Thank you,
Dominic Lovell
CustomWare Asia Pacific
We've downloaded and configures the Salesforce.com JIRA plugin. It works well. My question is why none of the Salesforce.com custom fields show up as available options in the JIRA Charting Plugin (http://confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin). All our other custom fields show up in that plugin and work well.
We're trying to create a report showing all our JIRA issues that are attached to a Salesforce.com account, and maybe another report that shows the accounts with the most JIRA issues. I was hoping to use the JIRA charting plugin for this purpose but that's not working. Ideas?
Hi Yoav, and thank you for evaluating our plugin.
Unfortunately, the particular type of custom field searcher that our plugin inherits is not of the same type the charting plugin relies on, which is why you cannot select the account custom field to be reported on. However, you can setup a filter and generate reports based on the Salesforce.com account you require, and generate one of the default charting reports based on this filter, filtering by that particular account.
I will raise a feature request on your behalf on the Atlassian Developer Network JIRA, so be sure to check back on our future releases that could implement this feature.
Thank you,
Dominic Lovell
CustomWare Asia Pacific
Hi CustomWare,
I have been evaluating your salesforce/jira plugin. While everything was easily set up through this document you have provided, I still have a question or two that will hopefully get answered quickly.
One of the biggest question is whether or not there is a create jira function for all the salesforce entities rather than just for the Cases. There is at least one other Salesforce entity where we would like to use it. I have tried to use the existing ".../CreateIssueFromSFCase!default.jspa?caseId={!Case.Id}" and replacing {!Case.Id}} with {!Opportunity.Id}, but as expected that did not work. Also, it appears that it references a variable called caseId, are there other variables to handle the issue illustrated here? Or perhaps there's another jspa?
If it's not possible, what would it take to have it implemented?
Please email me if you would like to start a thread about this.
Thanks,
-Will
Lithium Technologies Inc.
Hi Will,
Thanks for your the interest in our plug-in. I'll have one of our team members contact you regarding this.
Dominic Lovell
CustomWare Asia Pacific