Background
I’m working with multiple JIRA projects where we have one main project for our core application that handles both defects and feature development. We also have several client projects that use this core application, and each client project has its own separate JIRA workspace.
What I’m trying to achieve
I want to set up workflow transitions in the client projects that can automatically generate new tickets in the main core project. For example, when someone moves a ticket to “Core Bug Found” or “Enhancement Needed” status, I’d like a workflow function to automatically create a corresponding bug report or feature request in the core project and establish a link between the two tickets.
My question
Are there any existing workflow add-ons that can handle this cross-project ticket creation? If not, what would be the best approach to build this functionality myself? I’m particularly confused about how to reference the destination project within a custom workflow function.
I’ve done this exact thing at my company - Script Runner for Jira is definitely your best option. The post-functions make it super easy to create issues in other projects when workflows transition. You can map fields between tickets and it handles cross-project linking automatically. Just make sure you get the project keys and issue type mappings right in your config. Watch out for permissions though - if the workflow user can’t create issues in the target project, transitions fail silently. We added error handling because network hiccups sometimes cause timeouts. Takes some setup work upfront but it’s been rock solid once configured.
Automation for Jira (used to be called Automation Rules) handles this perfectly - no third-party plugins needed. I’ve built the same thing using smart values to reference different projects. Set up triggers on status transitions, then use the “Create Issue” action with project key variables. Just watch out for field mapping since different projects usually have different custom fields. One thing that bit me: make sure your automation actor has permissions across all the projects you’re touching. The “Link Issues” action works great for connecting parent and child issues in the same rule. We’re running about 50-100 automated tickets per week across four project combos and performance’s been solid.
we just use REST API calls in our workflow post-functions. takes a bit more setup but you get complete control over field mappings and error handling. you can reference destination projects by key and add conditional logic based on issue type or labels. works perfectly for our multi-client setup - just need someone comfortable with basic scripting.