How do I create a document creation plan in Jira?

[Dulari Vikas Pawar]

I want to create a Detailed Product Requirements Plan.

How do I do it using Jira?

[Gabriela]

Hi @Dulari Vikas Pawar, Jira Software tracks work items, it isn't a document editor, so a requirements doc doesn't really live there. Write the PRD in Confluence, which ships a Product Requirements template with the sections you'd expect (background, assumptions, user stories, scope); inside it you type /jira to link the epic and issues and /date for the target release date, so the spec and the delivery work stay connected. If you'd rather keep it in the Jira family, Jira Product Discovery is Atlassian's purpose-built tool for capturing and prioritising product ideas into a roadmap, and those ideas feed delivery epics back into Jira Software.

Product Requirements template

[Mary from Planyway]

Hi @Dulari Vikas Pawar 

Jira is a great tool for managing and tracking product requirements, although it doesn't provide a dedicated "Product Requirements Document (PRD)" template out of the box. A common approach is to combine Jira issues with Confluence (if available) or structure your work directly in Jira.

Here's one way to organize a detailed product requirements plan in Jira:

• Create an Epic for the feature or initiative.

• Add Stories to describe each user-facing requirement.

• Break stories into Subtasks or Tasks for implementation work.

• Use custom fields for details such as acceptance criteria, priority, business value, dependencies, and target release.

• Link related issues to capture dependencies and blockers.

• Track progress using boards, timelines, and dashboards.

If you have Confluence, you can keep the detailed PRD there and link it to the corresponding Jira Epic, while Jira handles planning and execution.

If your requirements plan also needs a visual roadmap and scheduling, I'd recommend Planyway for Jira. It complements Jira by providing interactive timelines, Gantt charts, cross-project planning, workload management, and dependency visualization. This makes it much easier to turn product requirements into an actionable delivery plan and keep everyone aligned on milestones and deadlines.

[John Funk]

Hi Dulari - Welcome to the Atlassian Community!

(You, too, Gabriela!)

As Gabriela said, Confluence would be the place to create that. However, you can use Rovo to help with that based on a project/space in Jira or even on a Jira Work Item, depending on where you have the base information. You can start there, engage Rovo and asked it to create a Product Requirements Document in Confluence using the Product Requirements template and using the information in the Work item in context.