You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have teams that complete work on Jira Service Desk tickets and also complete Jira Software issues. We have some teams that receive their work items off of kanban boards, some work off of dashboards, and other teams work out of their project boards. Our Jira Service Desk users don't typically work out of service desk queues as they receive work items across multiple Jira Service Desk projects.
I am just looking for feedback from anyone else that might have an organization working similar to this. What solutions have you found work best for teams to be able to see all of their work in one place with these two products? Any recommendations you can provide will be much appreciated - Thank you!
Hello @Angel Osberg . I have been working in similar conditions due to our clients open its issue in JSD and the problem is followed by a new bug in Jira Software Kanban.
My main recommendation is approach Jira automation in order to replicate the issue without affect the SLA. However, I find several problems in this method. For example, if the original ticket is open with a attachment, It can't be copied to the Kanban, you will see a typical "error image". In order to avoid that, I had to give access to JSD to support team in order to check the original information.
There are multiple request about that.