Loading Profile...
Error message in Jira Salesforce.com Case Numer (in Red) is uneditable
Displaying the following message:
( Customware-CRM-plugin ). Error message from Salesforce.com : INVALID_QUERY_FILTER_OPERATOR : Subject, OwnerId from Case where id = '00021431' ^ ERROR at Row:1:Column:71 invalid ID field: 00021431
Cannot edit it to remove the error message and now the Sync To Jira function in Salesforce says that it cannot find the Jira Bug.
We have the plugin for Jira 3.11+ installed.
Also sometimes the Case Search popup in Jira does not allow you to click to select the relevant Case. Why is this? (It seems after further investigation that the Case Search does not like some special Characters like Quotes or Speech Marks. Is this a bug?)
( Customware-CRM-plugin ). Error message from Salesforce.com : INVALID_QUERY_FILTER_OPERATOR : Subject, OwnerId from Case where id = '00021431' ^ ERROR at Row:1:Column:71 invalid ID field: 00021431
Cannot edit it to remove the error message and now the Sync To Jira function in Salesforce says that it cannot find the Jira Bug.
We have the plugin for Jira 3.11+ installed.
Also sometimes the Case Search popup in Jira does not allow you to click to select the relevant Case. Why is this? (It seems after further investigation that the Case Search does not like some special Characters like Quotes or Speech Marks. Is this a bug?)
I’m anxious
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
The issue regarding special characters not supported during Case Search in JIRA has been resolved in Salesforce.com Plugin for JIRA version 3.0.2.
Here is the related JIRA issue.
The company says
this answers the question
-
Inappropriate?Thanks. Email sent with further details. -
Inappropriate?FYI, We are loving the plugin despite the little hiccups.
-
Inappropriate?Hi there Matt,
Can I ask which version of the plugin you are using? Is it the latest (version 3.0.1)?
The previous version had a known bug with the unclickable links with special characters, but I believe this has been fixed in version 3.0+.
Regarding the error, I will ask the guys here but it would be useful to know which version you are using first.
Cheers,
Jen -
Inappropriate?I believe it is version 3.0.1 (without checking Jira). I selected the download that was for Jira version 3.11+ so assume when I did, which was about three weeks ago, i was selecting 3.0.1.
We are running Jira 3.13 -
Inappropriate?Hi Matt,
Can you please check your Salesforce.com to JIRA Mapping Configuration and see if you have mapped Case Number to the custom field of type Salesforce.com Case or Salesforce.com Case (with Case Number). If it is mapped, please delete these mappings. These custom fields are supposed to be handled internally as they need to store the Case ID and not the Case Number.
Now try creating a case in Salesforce and save it to JIRA and let us know if this solves your problem.
Unfortunately you will have to delete the previous JIRA issues that has the error and try saving the cases to JIRA again via Salesforce.com.
Regards,
Allan2 Comments Add a comment
This answers the question
-
Yeah the deleting the Mappings allowed the Save to Jira to work and I presume the Sync to Jira will now work as well. The only outstanding issue is the special characters that are not supported during the Case Search in Jira. SF Cases with Subject lines containing either a '[word]' or "[word]" (Speech marks and Quotation marks) cannot be selected until the speech or quotation marks are removed from the SF Case Subject line. Again we are running the latest Jira Plugin using Jira v3.13 -
Hi Matt,
We have replicated the issue for double quotes on SF Case subject line. The single quotes works in the current version. We will fix the bug on double quotes in the next release. -
Inappropriate?The issue regarding special characters not supported during Case Search in JIRA has been resolved in Salesforce.com Plugin for JIRA version 3.0.2.
Here is the related JIRA issue.
The company says
this answers the question
EMPLOYEE
EMPLOYEE
EMPLOYEE
