I would like to explore the use of JSM as the primary place bugs and issues are raised, both by our customers and internal support team.
Our Development teams are using a Company-Managed Jira Software Kanban Project to manage their dev workflow.
Rather than the Dev team having to work within two Projects, I am wanting to know if issues that are raised on the JSM can be mirrored and automatically created in another Jira Project?
I know I can "Move" an issue to another project, but this is a manual process.
Thank you for your help!
Yes, you have multiple high-level options here to accomplish your asks -
1) I believe you can use "Automation for Jira" add-on (it is an add-on free in the Jira Cloud Premium account) to setup automation rule to create issues in Jira Software project(s). It is assuming that you already have your CLOUD env setup for both JSM and Jira Software in the CLOUD. If your two application environments are different (i.e. JSM is CLOUD based and Jira Software is Data Center based), then you will also setup application links between those two environments.
2) Customize your JSM workflow and use Post Function calls to create issues in your Jira Software projects with custom scripting or paid third parties add-ons for your Jira env. Two add-ons options are -
Jira Misc Workflow Extensions (JMWE) - https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions-jmwe?hosting=cloud&tab=overview
ScriptRunner for Jira - https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=cloud&tab=overview
In our Data Center on-prems envs for JSM and Jira, we use the 2nd option to auto create issues in Jira Software/JSM projects when JSM issue is created or transitions into a specific WF status via customized JSM WF's post function call. In the calls, we also link those auto issues back to the original JSM issues automatically.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Hi @Ben Scott
in addition to the two solutions @Joseph Chung Yin mentioned, you can also use an issue sync app for your scenario.
If you only care about creating issues in another project, I'd probably go with one of the Automation steps, described by Joseph.
If you also care about synchronizing updates after the create either uni- or bidirectional, I'd recommend to have a look at one of the issue sync apps in the marketplace.
PS: I'm part of the Backbone Issue Sync team.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events