Problem 1: Asset-based team assignment fails across projects
We have an automation in Project 1 that can be manually triggered to create an issue in Project 2. The issue should be assigned to a team based on data stored in Jira Assets (not Jira Teams). We're using a custom field here that is linked to an object schema that contains different teams, and we're trying to populate this field using both the specific asset key or Name LIKE "Team 1" when creating the issue using "Create work item with request type" in the automation.
This works perfectly fine in our sandbox and also within the same project. However, when the automation creates an issue in another project, the field fails to populate. It's important to note that teams in Project 1 should not be selectable in Project 2 and vice versa and this separation works fine in the sandbox.
Problem 2: Automation trigger on “Work item created” doesn’t fire
As a workaround, we created another automation in Project 2 that triggers on the “Work item created” event within that same project. The idea was to handle the assignment after the issue is created. However, this automation does not trigger for issues created via the first automation — only for manually created issues or those created through other means.
We’ve verified that the workflow includes the “Issue Created” event in the Create transition, so it should be firing correctly. Still, the automation doesn’t respond to these issues at all.
Has anyone experienced similar issues with Jira Assets and cross-project automation?
Apologies for the messy question — we’ve been troubleshooting this for a while and haven’t found a clear solution.
All the best!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.