Company-Managed Scrum board - multiple projects - cannot move tickets

[Frank Lacalamita]

Hello,

     Here's my challenge, i have a product team project.  Once they completed their flow and it's in a "ready for dev" status, i am able to see it in my dev team project backlog.

I was able to accomplish this via the query filter setup.  I move the ticket from the backlog into my sprint, and i start the sprint.

The ticket show's up in the "to do" column but i cannot move it to my "in progress" column.  I think it's because the ticket is still associated with the product team project and the statuses i configured in my dev team workflow do not exist.

Is their a way for me to move the ticket using the dev team statuses?

thank you,

[Tim Fricke]

Is there a recommended best practice to mitigate duplicates since this will be used by customers as well as sales teams?

[Nic Brough -Adaptavist-]

Always refer to issues by their JIRA id, not some arbitrary number that doesn't mean anything to JIRA.

[Jaime S]

Also, Tim, if you set up your notification schemes correctly, if your users reply to the notifications, the subject should contain the issue key and a comment should be created instead of an issue.

[Tim Fricke]

For internal teams that makes sense, but how would a customer know what JIRA id to input? The customer piece is where I'm getting hung up. Does that make sense?

[Nic Brough -Adaptavist-]

Yes. But where does the customer get "bug 22" from? If they're inventing numbers, you're likely to be a bit stuck at first, but you could change the procedure of feedback - "Thanks for raising your bug 22, we have it logged as PROD-34"

[Nic Brough -Adaptavist-]

You need the email subjects to contain the issue id.  Bug #22 is just a string that doesn't mean a lot to JIRA.  If your users had included PROD-36 in the subject, it would be able to match them to the issue.