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
My apologies if these questions have been asked and answered. I am new to Product Discovery and have 2 questions.
Thanks
Hey @David !
I think you'd need to set up some kind of automation to create a new ticket in your roadmap project when some kind of trigger is met on the JSM project.
For example, you could move the JSM ticket to a new status "Feature request". This then creates a new ticket in your roadmap and can be configured to copy over relevant data & link the tickets.
You should also consider the reverse scenario (which probably happens much more often), where an idea already exists and you want to link the JSM ticket to the existing idea. In this case, you'd add the JSM ticket as an insight to the idea, which creates an "added to idea" link on the JSM ticket.
- C
Chris, I like this idea. We already do this when support tickets are set to a certain status and this triggers the creation of a development ticket.
Hi Drue
We had the same issue and solved it with the automation functionality like that:
Perhaps thats helps you :)
I was suggesting this to my product team as it didn't seem accurate to have request automatically created to ensure you don't receive a lot of noise, but what I have not solved is how does the customer receive communications on the status of the request once it now exists in discovery? Since there is no ability to communicate back and forth as you can in JSM.