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
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 service desk tickets that get linked to product boards for development work. Is there a way for reporting to not receive duplicates when pulling information. For instance, when I pull all open tickets from the previous weeks I get the project issue and desk issue. I want to get everything at once. I know I can write a query. Just wanting to know best practices when linking product and desk tickets
When you duplicates, can you explain more and what you mean by 'getting everything at once'. For Service Desk issues, I create a filter to pull only Service Requests and display the link in my results to see the Jira Product Board linkage.
You are on the right path - you should most likely write a JQL that excludes issues with issue link being Duplicates.
And yes I would also use issue linking between JSM and JS projects.
Depending on how the issue linked issues are connected you might want to use or add other issue link types :P
Hi Krystal - can you describe the exact process that is happening now (including the issue creates) and what you are then hoping to see?
Recommended Learning For You
Level up your skills with Atlassian learning
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Managing Permissions in Jira Cloud
Sharpen your skills at configuring and troubleshooting permissions in Jira Cloud with this free course.