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

How to track a JIRA SD ticket that's been assigned from one project to another project

Robert Levine

So, I'm managing a team that uses JIRA SD (for the sake of this question, let's call this team the "Scrubs") and they use a project called "Scrubs". We receive a ticket that we need to move to another team's queue. They're called the "Superstars" and use a similarly named project.

So now, we've Moved the ticket from "Scrubs" to "Superstars" but we need to keep an eye on the "Superstars" ticket so that we can ensure it gets reviewed and followed up on.

I need to build a queue or a report that shows me all tickets that have been moved to another project so that I can ensure they eventually get moved back to my queue for closure.

Any ideas?

Accepted answers

All comments

Joe Pitt

When you move a ticket it maintains the old number. If you know it you can simply search for it.

Robert Levine

That would help if you knew the number and wanted to actively search for it. But, I, as a manager, will not have visibility of all of my team's tickets - and still want to ensure that everything that my team "touched" gets handled correctly.

So, really looking for a way to do it via a queue or report.

Jack Brickey

So you seem to be talking about JSD but posted this in Jira Questions. If you are actually talking about JSD IMO, and others, it is best not to move the ticket at all but rather:

create a status that applies to issues that need superstars
transition the issue into the superstar status
create a linked issue in the superstar project
use automation to have the status 'follow' the linked superstar project.

Robert Levine

Thanks Jack. That's the solution I was getting around to as well - when testing moving the ticket from one project to another and then back again, it didn't maintain the original ticket number anyways... so ticket # was incrementing.

I just have to figure out the automation bit now. Love being a JSD newbie!

Jack Brickey

great! there are some good threads out there for automation. just search the Community for connecting JSD and JSW w/ automation.

Robert Levine

Well, the automation bit isn't exactly what I'm looking for, now that I think of it.

Even if the linked ticket is closed, I do not want to automatically close our team's ticket. But I want to be able to keep track of the status of the linked ticket on all of the open tickets in my own queue.

So, if a ticket in my queue is linked to another, I want to be able to see the status of the linked ticket so I can then action my own ticket in response.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server