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; } } }

Can you have the same issues reflecting on different projects?

jessica.hall

I have one project created under Jira Service and I've created a new project under Jira Work Management to utilize the calendar feature. Is there a way that both projects can reflect the same issues for specific users/individuals? OR is there a way that once an issue is submitted under the Jira Service project, it automatically gets pushed to the Jira Work Management project?

Accepted answers

All comments

Jack Brickey

You can certainly create an automation to clone an issue to another project.

trigger issue created in the JSM project
condition - as needed to ensure the clone action only occurs as desired
action - clone issue into JSW project

you will need the rule to be global or multi-project.

the question I have is - why are you doing this? What are your goals? On the surface it seems a bit unnecessary but I don't understand the needs.

Ste Wright

Hi @jessica.hall

You can use Automation, although I'd use this only if...

You have Premium, and more significant executions for this kind of rule
You're on Standard but have a small number of tickets

^ Automation would let you...

Clone from JSM to JWM (you could then close the JSM ticket), or...
If the tickets should both remain open, Automation can also send updates bi-directionally - eg. status changes, comments, etc.