Hi @susan_murphy,
If this would be a tooling question, I'm sure it would not be immediately related to JSM - but apart from that ...
With the arrival of Jira Product Discovery some time ago, Atlassian has a pretty neat separation of backlogs in place for this. As long as something is pretty much "an idea" being explored, its natural place is in the product backlog. This is where it can be handled as an opportunity, possible solution(s) can be explored and designed before it goes in the delivery backlog. That story very much matches what you describe: separate backlogs for product ideas (in JPD) and for delivery work (in Jira).
Obviously, there is no golden rule or strict guideline that you need to set things up this way. The separate tools do offer dedicated capabilities to manage those different stages of work rather well and connect pretty well too.
If you do want to manage the entire process from ideation to delivery inside Jira alone, you would benefit from building the steps from idea to delivery into your workflows. Bear in mind that - in this scenario - your (delivery) backlog will be populated with - sometimes plenty of - items that will never be built.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.