Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 12

Introduction - Overall Process of Requirements Management in Confluence & Jira:

  • Use Confluence’s powerful editor to create multilevel templates (e.g. FRS/PRD/TRD/SRS/MRD/BRD) and add images, diagrams, macros, formulas, etc. to them.and customized templates to create your PRDs in Confluence

  • Use Jcreate to identify the structure of your requirement documents (headings, lists, bullets and so on) to automatically turn requirements into turn your requirements to issues in Jira, linked to your content.Once

  • Approve the requirements have become issues in Jira, you can use Jira’s powerful workflow to add Review and Approval phases to your requirements.Plan and build your product’s roadmap in Jira.

  • Implement your requirements by creating derived tasks for SW, HW and any other team. Create the requirements and trace them, create a hierarchy of issues attached to your PRD.

  • Manage tests in all levels for full requirements coverage.

  • Apply traceability views from all levels of your work items.

With Jcreate, you can have the full Jira experience within Confluence - Creating Jira issues from Confluence page is old news, however, it is very basic. The only values you can supply are Jira server, Project, Issue Type, Summary, and Description.This is quite limiting when your Jira issues has required fields or other customizations as these standard scenarios are not supported. all fields are supported (see supported fields), required fields will be marked with “*” etc.

Click here to see how it works!

...