nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Would you fully document stories in JIRA alone?

nick verze

Our dev team are baulking at the product teams use of linking requirements from confluence into our JIRA stories.

Wondering if any of you out there have successfully documented software requirements for stories only using JIRA?

More specifically, has anyone been able to document Story, Busines rules, Acceptance criteria and UI within a JIRA without using links to other document tools (e.g. Confluence or Sharepoint)?

Comments

Nic Brough -Adaptavist-

You can, and I've seen it done in a couple of ways. One was text fields on stories to capture the various fields, another was to have overall stories with the other data broken out into sub-tasks for individual authorisations/testing etc

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira