0

I'm looking for help around Jira and Salesforce. I currently have the Service Rocket plug-in working, cloud, with articles. Below is the user story.

Questions:

  1. Can the text formatting in Jira be preserved coming over to the SFDC rich text field?
  2. Can Knowledge's Data Categories be set in the API?

User Story

As a CSR I would like to see Jira Known Issues as SFDC Articles so that we don't have to search different areas of salesforce and just view all current how to articles with known issues and be in one place.

  • When an issue of Project = Known Issue and Type = CSA incident is created in jira, the system should then create a corresponding Known Issue SFDC Article, as per the field mapping.

  • When I view the article tab in Salesforce I can select one of the sub-tabs, data categories, across the top and choose a category to narrow my search

  • When an issue is updated in Jira, then those updates need to appear in SFDC's article, pre the mapping.

  • When a new attachment is added to an Issue in Jira, that attachment needs to be attached to the SFDC article.

  • When an issue is closed in Jira, then the corresponding article in SFDC is deleted, so that no closed Known Issues are every seen by a VXA.

Mapping

  • Why not use a unified index and display both in a panel within Salesforce? (Jira and Kb Articles + any other data sources if any) – glls May 5 '17 at 21:02
  • However you would need to lookup for a managed package in the AppExchange to test. – glls May 5 '17 at 21:07
  • Glls - interesting but how would the search work then if there is no data housed within salesforce knowledge? – Fifedog May 5 '17 at 21:54
  • through the unified index - the search queries an external service to fetch the data from confluence Jira – glls May 5 '17 at 21:55
  • 1
    Let us continue this discussion in chat. – glls May 5 '17 at 22:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.