Charles Pham's dashboard

Hi Robert,

Our team are currently investigating this problem for you and will respond in a timely manner.

Kind Regards,
Charles

Hi Ali,

What I suggest you do is create a standard text field in SFDC.

Create a mapping between this field and your JIRA Status field.

Remember to add in the "SFCaseUpdateListener" - http://www.customware.net/repository/...

Please note this only works with the Salesforce.com Case or Salesforce.com Case (with Case Number) custom fields.

Synchronization will not work with the Salesforce.com Multiple Case or Salesforce.com Multiple Case (with Case Number).

Kind Regards,
Charles

This problem has now been fixed and will be shipped in our next release. Further details can be found at - http://greenhouse.customware.net/jira...

Hi Ali,

What I suggest you do is create a standard text Custom-field in JIRA (Maybe call this "SFDC Prioriy"), then create a mapping between this field and your SFDC Priority Field.

Kind Regards,
Charles

Hi Richard,

Unfortunately this plugin was not designed to cater for the above specified scenario. There is a workarounds that you could try.

Customers can simply use Salesforce as they normally would. From there users who do have access to JIRA (internal staff) can then save/sync these issues on behalf of them.

If you would like to discuss this further, please email - sfdc@customware.net

Kind Regards,
Charles

Hi Matt,

The above warning means that if you are using any custom-fields from the plugin which can store multiple values at the same time (i.e. Salesforce.com Multiple Case Customfield), syncing will not work.

The second part of the warning means that you can not map out multiple JIRA customfields to the same Salesforce field (i.e. mapping JIRA Customfield 1 and Customfield 2 to one single Salesforce Field A). One to one mapping of fields should work fine.

Let me know if there is anything else I could assist with.

Kind Regards,
Charles

Hi Matt,

There are no current plans to extend the Salesforce/Confluence plugin to call info into Salesforce.

We could however certainly develop something for you to met your exact needs. Please email info@customware.net with your requirements and our team will see how we can assist.

Kind Regards,
Charles Pham

Hi Matt,

Thank you for using our Plugin!

I have a workaround to auto populate the JIRA Key into a Custom Salesforce Field.

Basically what you need to do is:

1. Install the JIRA Suite Utilities Plugin - http://confluence.atlassian.com/displ...
1. In JIRA Create a "Text Field" Custom Field and call it "JIRA Key"
2. Modify your JIRA workflows so that on the "Create Issue" transition, add the "Copy Value From Other Field" post function.
3a. For the source field select: "Key"
3b. For the Destination field select: "JIRA Key".
Make sure the new post function sits below the "Creates the issue originally" and "Re-index an issue to keep indexes in sync with the database. " post function that is there by default.
4. Publish this workflow onto your JIRA projects.
5. Assuming that you already have a Custom Salesforce field to store the JIRA Key. Using our SFDC Connector Plugin, create a mapping between the SFDC Customfield and the "JIRA Key" customfield.
6. Lastly make sure that you have the - "SF Case Update Listener" configured - http://www.customware.net/repository/...

By adding in the post function above, we have created a custom field that will contain the JIRA key. From this JIRA key we are able to map to the SFDC Customfield. Whenever the JIRA issue gets updated, the listener will update the SFDC custom field to the JIRA key.

I hope this helps you out and feel free to let us know if you need any further assistance.

Kind Regards,
Charles Pham

Hi Dan,

I would imagine that this is something we will need to make a new release to fix. I will get the development team to look into and will reply again shortly.

Kind Regards,
Charles

Hi Leah,

Thank you for raising that issue with us. This appears to be a bug with the plugin. I will get the development team to see if there is a workaround.

Kind Regards,
Charles