Comments
-
This is an interesting scenario, especially because the challenge isn’t really the automation itself; it’s deciding what information should move between internal technical teams and customer-facing teams, and in which direction. We’ve seen similar challenges in Salesforce & Jira workflows, where support teams need…
-
Love that you’re going all in on the Atlassian ecosystem — that’s when the real benefits start to show A few “game-changer” things I’ve seen teams underuse: * Automation with clear guardrails (start small, solve repeatable pain first) * Standardized issue types + minimal required fields to protect reporting later *…
-
Great question — this is very real. If I had to pick one, it’s #5: Configuration sprawl. After a few years, Jira becomes a collection of: * Custom fields created “just in case” * Slightly modified workflow clones * Team-managed projects multiplying * Automations stacked on automations The hard part isn’t cleaning it up —…
-
@Dirk Ronsmans we have a product called Sinergify that integrates Salesforce and Jira. On the Jira side, we use a Jira plugin for bi-directional updates. For Jira users, the plugin provides additional capabilities such as: Creating Salesforce records from Jira, manually or automatically based on rules. Bulk creation of…
