SF Case Update Listener stops working

Jen,

I am using Salesforce.com Case (with Case Number), not multiple, which I believe is correct. I was previously updating properly, so I have been trying to pin down why it has stopped.

I had our IT pull the logs, but they weren't much help, the last entry was from April 2008. Is that normal for the logs to not be upadting? Do you have any suggestions of what to try next?

Thanks,

Greg

Hi Greg,

No those logs look incorrect, JIRA generates log entries all the time. Are your IT guys looking in the right place? Mine is in the bin directory but it could depend on your JIRA setup. You can check http://confluence.atlassian.com/pages... for more details but navigating to your JIRA administration screen -> System Info (at the bottom of the left nav) will show a parameter called "Location of atlassian-jira.log" which should tell you where the instance is writing to.

Cheers,
Jen

Jen,

I was able to obtain the correct logs, and have now made some headway, but still have a couple questions:

1. One of the fields I was trying to change was generating the following error:

2009-10-20 10:10:28,588 http-10.10.1.8-80-Processor16 ERROR [salesforce.jira.listeners.SFCaseUpdateListener] java.lang.Exception: Unable to create/update fields: CaseNumber. Please check the security settings of this field and verify that it is read/write for your profile.
java.lang.Exception: Unable to create/update fields: CaseNumber. Please check the security settings of this field and verify that it is read/write for your profile.

For some reason this was preventing any other field from being updated, as I removed that field from the list, and remaining fields began updating properly. Is that normal behavior that one field can block all from updating?

2. One of the key fields I am wanted to update is status, but it is generating the following error:

2009-10-20 10:10:26,463 http-10.10.1.8-80-Processor16 ERROR [jira.mapping.service.SFSaveJiraFieldServiceImpl] No managed to set the value of On Deck to field of status
java.lang.IllegalArgumentException: argument type mismatch

It is currently defined as a pick list with the same values as my Jira statuses, On Deck for example is a valued SF status. What do I need to change to get things working?

Thanks,

Greg

Hi Greg,

1. Yes if there is a problem with one field mapping, the synchronisation is blocked completely for that issue. Just from the error message, looks like that field has a security issue? Do you have full access to it? We have also seen this error with a picklist field in Salesforce whose options depended on the choice of a picklist in another field - JIRA could not sync to the secondary field. Could that be your problem?

2. The status only syncs from JIRA to Salesforce due to JIRA not allowing programmatic jumps through the issue workflow (e.g. can't jump from "Open" to "closed" and skipping multiple steps in between), Which direction are you trying to sync?

Cheers,
Jen

Jen,

Thanks for all your help, I think I have sorted everything out now.

Greg