nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moving issues from one to another project

Yojana_xgl8jl

Hi,

I want help on two points :

Scenario : There are two SD projects used by my company. One is Customer Service desk project and other one is IT service desk project.

We want to create/replicate issues which has status "Move to IT" once CSD seeks help from IT.

If CS marks status to "Move to IT" it should create new issue in IT project and should start SLA associated with that project.

Note : CS do not have access to IT project.

Comments

Julie d_Antin _Elements__bsgnak

Hi @Yojana ,

Our app Elements Copy & Sync could help you. Looks like you are on Server, and our app allows copies of issues to be made in other projects, even if users don't have permissions in the project. Check out this tutorial for escalating issues.

This video also gives you an idea of how it could work to create an issue in another project: https://youtu.be/nscBfpb2Xno

John Funk

Hi @Yojana - You can set that up with an easy Automation For Jira rule. Here's some more information on Automation if you are not familiar with it:

There are two types of automation:

Global: In the Free version, you get 100 executions per product, per month
Project: In all versions, you get unlimited executions per month

Automation Basics: https://www.atlassian.com/software/jira/guides/expand-jira/automation

You can do this via global rules to apply to all projects also. You'll need to be a Jira Admin/Site Admin, go to Jira Settings > System > Automation Rules (left-hand menu).