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 are using Product Discovery (PD) to drive product innovation at our organization with the intent that delivery tickets in various software projects may then be created from an idea.
We don't right away know who the assignee of those ideas / delivery tickets should be, but we do know the team that should triage and develop them. We've tried a few things to bridge the gap between assigning a team to an idea and assigning an individual to a delivery tickets, but there doesn't seem to be a clean way to do this besides potentially a highly complex automation.
The desired solution would look as follows:
In this way, when a team is assigned to an idea and delivery tickets are created for that idea, every delivery ticket would be assigned to the team from PD and we could look at a saved filter for each team that shows unassigned issues. Then, we could assign issues to the team member for development.
Hi @Harrison Magee -- Welcome to the Atlassian Community!
I have not used Jira Product Discovery (JPD) with delivery teams in that way, nor have I learned of others doing so. Although a "team" field could be added to a JPD project, it would have no meaning to the rest of Jira...unless someone manually linked to Jira projects' issues (or did so with automation rules).
Instead I have observed that after ideation, Ideas are added to a JPD project, followed by identification of one, or more, delivery teams in a "Team" field. Then the team members would add an Epic to their Jira project, and link it to the Idea on the Delivery tab. That decentralizes the management of the work items to implement the idea to the delivery team(s) doing the build work.
I suspect what you described is possible if a placeholder, non-JPD project was created (e.g., a Software Project with a Kanban board), and the people using the JPD project would add "delivery" issues into it, linking them to the Idea. An automation rule could then move the issues to the target delivery team's Jira project.
That approach seems like a "push" rather than a "pull"-based model, and so I recommend discussing the problem you are trying to solve with your product management and agile coaches to learn their suggestions.