#Create A Case4 personnes en discutent

Update which I feel this will be helpful for the community, after a few rounds of Salesforce-Jira integrations, here's what's consistently saved us troubleshooting time: 

1. Don’t sync everything: Concentrate on business-critical fields (Case, Bug, Story, Priority, Status, Assignee, Resolution). A leaner scope will result in better performance, lower API usage and less conflicts. 

2. Go event-driven over scheduled polling: Keeps Support, Engineering, and Product on the same current data. 

3. Map fields before you build: Picklists, Statuses, Priorities, Record Types rarely map 1:1 across systems. 

4. Assign source of truth per field: Avoid update loops e.g. Engineering owns Resolution/Sprint, Support owns Customer Impact/Case Priority. 

5. Think about API limits. Bulk updates burn your allocation fast. Use batching, retries, error handling. 

6. Filter attachments/comments: Not everything should cross systems; filter by visibility, user type or keywords to keep internal notes internal 

7. Support multiple Jira projects/instances: Configurable mapping scales better than hardcoded routing logic 

8. Monitor failed syncs proactively: Logging + retry queues + alerts catch issues before they silently break workflows 

For

a Salesforce Jira connector, handles bi-directional sync without middleware and covers most of this out of the box. 

What I have seen from my personal experience: 

• Jira user-based price skyrockets as companies look to scale.
• Organizations require a single Salesforce Case to sync with numerous Jira issues but not all connectors enable this natively in SF.
• Parent-child Case circumstances necessitate workarounds particularly for enterprise support teams.
• Validating skills beyond the demo - real-world workflows help to identify shortcomings.
• Comment synchronization is an area that is often overlooked, yet it can have a significant influence on collaboration if it is not trustworthy.
• Also, don't just ask if it's 'bi-directional'; inquire about whether it's genuinely real-time and how it handles conflicts and retries.

These are just patterns I've observed across customer conversations and implementations. 

Dear Support Team,

I hope you are doing well.

I am currently unable to log in to our Salesforce account. When attempting to log in, I receive a message stating that our company's Salesforce account has been suspended.

Kindly review the issue and reactivate our account at your earliest convenience so that we can continue our work without interruption. 

Link: 

Account Username: amyhlll-wn0h@force.com

Please let me know if any additional information is required from our side.

Thank you for your assistance.

Best regards, 

Amy Hill 

Hi Trailhead Community, @Kübra Muhtar

I'm currently working on the "Create a Case Escalation Rule" step in the Set Up Case Escalation and Entitlements project. I'm using my hands-on org for this challenge. 

When I try to verify the step, I receive the following error message: 

I’ve carefully followed all the steps as outlined in the project instructions, ensured that the 

Account Name is Pyramid Construction and the Type is Product Support

. I have also tried the following troubleshooting steps: 

• Recreated the case multiple times
• Cleared browser cache
• Tried in different browsers (Chrome, Edge, etc.)
• Relaunched the org and re-did the steps from scratch

Despite all this, I still receive the same error when verifying the challenge. Has anyone else faced this issue or can suggest any other fixes? Any help would be greatly appreciated. 

Thank you in advance for your support! 

Best regards, 

#Trailhead Challenges  #Certifications  #Case Escalations  #Escalation Rule  #Create A Case