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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I went through the first steps of experimenting with JPD, with my fellow colleagues from our Support team.
We're using Zendesk, and we're used linking tickets to Jira issues. Via workflow post actions, tickets are automatically updated when the dev team took some action. For customer's feature requests, we are more or less just improvising, with Confluence lists etc.
After playing around with JPD, the Support team first and foremost said that they liked JPD for being simple and fun to work with! :-))
But a few details seem missing for our best practices and workflows: