Queue for two different project keys

[marianna_taborda]

Hello guys!

I'm moving from a shared project to a dedicated project to my dept only. However, I'm having an issue where two issue types on the shared original project are split between depts. and both depts cooperate on these tickets. 

These are tickets that we receive from high level management who sometimes don't truly know under whose team does the query fall, or letters they receive and we need to investigate before ascertaining ownership. 

Is there a way that while on transition to a dedicated project, I could display to my SMEs the tickets they have escalated on their other SD & those that are in progress but assigned to them as well? Basically, like the Jira filters where we can look up issues from different project keys, can I mimic that on a Jira queue? 

Thank you!

[marianna_taborda]

Thank you @Nic Brough -Adaptavist- & @Brant Schroeder !

This was more or less what I tried to do. I wrote the queue in SQL, in the new project but linking it to the previous one. So, I'm in project B and I wrote it like 

project in (A) AND issuetype = ("EE", "Customer request") AND assignee in (abc)

The issue here is that I'm unable to get any tickets from project A into the project B - and I know I have those tickets as I have access to both projects. How can I try and sort this? 

[Nic Brough -Adaptavist-]

Ah, hang on, you're trying to use the filters inside queues.  This will not work, because queues are specific to a project. 

Look at the help-text above where you put the JQL in.

You will have to work outside the queue and a single project.  You need to write JQL in a search, save it as a filter, and work with that in the issue search and maybe dashboard gadgets, and Software boards.

Projects cannot share queues because the queue (and SLAs) for projects could be different, so an issue in A might be queued and have its SLA calculated totally differently to one in B.

[Brant Schroeder]

@marianna_taborda I my previous post I provided some helpful links in this.

[Brant Schroeder]

@marianna_taborda 

Here are two options for you.  

1. Create a filter that identifies the issue from the other project and have your SMEs subscribe to it so that they get daily notifications of issue that have been created outside of their current project.
2. Create a filter that brings all their work together and use it to create a dashboard.  They could then work off of the dashboard until the other project is closed and they begin working out of a single project.

Helpful information:

• https://support.atlassian.com/jira-software-cloud/docs/manage-filters/ 
• https://support.atlassian.com/jira-software-cloud/docs/work-with-dashboards-in-jira-cloud/ 

[Nic Brough -Adaptavist-]

Hi Marianna,

You need to put some data on the issues that you can filter on.  You may already have something (can you identify what one group needs to see by status?  Assignee?  Reporter?  An escalation flag?).  You can build a filter for each group based on "Project = X and group-indicator = Y"

If not, then there's one easy trick we use a lot.  Many filters I see (or queues of course) use "Project = X OR label = Y".  This just means we can get another team's attention one one of our issues by having them mention us by label.