Backlog in Jira

[Tinker Fadoua]

Good Day everyone,

Since Jira Product Discovery (JPD) allows users to collect, create, then link their ideas to Jira work items.

If teams can share their ideas in one centralized place, I feel there won't be a need to create work items in backlog when some of them will never be worked on. Not to mention how some backlogs have a huge list of work items that were never or will be prioritized.

Do you anticipate in the future Atlassian can remove backlog from Jira?

Best,

Fadoua

[Aaron Morris]

I don't think so. JPD doesn't replace the backlog, but it does help prevent work from being added to the backlog prematurely. (IMO)

[Tinker Fadoua]

Thank you for taking time to share your input @Aaron Morris !

[Dirk Lachowski]

You are maybe confusing the sprint / work backlog with the product backlog. JPD can (and should) replace the later. You still need the former in Jira.

https://www.atlassian.com/agile/project-management/sprint-backlog-product-backlog

[Tinker Fadoua]

Thank you @Dirk Lachowski  for sharing your input! I am definitely referring to Product Backlog as I am not seeing the need for it.

[Lucas Modzelewski _Lumo_]

I don't think so.

JPD ≠ a software or work project.

I treat JPD as an ideation space. Only when the idea is mature and clearly defined do I move it into a software project.

Before JPD, I used Epics for ideas, but those would just sit in the backlog until their descriptions were refined enough to actually start working on them.

Also, having a separate space for new ideas helps improve clarity. For example, new team members might propose ideas that were already discussed and rejected in the past. Using JPD with a limited number of creators can help reduce duplicate tickets. It also allows the PO/PM to prioritize more effectively, using data to make informed decisions.