Requirements, User Stories and Acceptance Criteria without Confluence

[Beth Shutt]

Does anyone have an example of including requirements within Jira, without linking to Confluence?  On our team, we prefer to keep as much as possible on the Issue ticket in Jira and not use a link to a confluence document.  We're a small team - looking for a one stop shop, so to speak - looking and updating in ONE place for our BA and our Developers. 

I would rather not attach a document, as i can't update it dynamically.  Has anyone done this successfully? 

Thank you!

[Oleksandr Siryi_Railsware_]

Hey, @Beth Shutt 

As @Summer Hogan has mentioned, checklists are a nice tool for keeping requirements inside issues. You can use Smart Checklist for Requirements or Acceptance Criteria, or you can save certain checklists as templates and add them automatically. This is a nice solution for always having Definition of Done checklists. 

[Adaeze_Jude_HEROCODERS]

Hi @Beth Shutt 

You can use the Issue Checklist for Jira free Add-on to create acceptance criteria within the Issues.

It provides you with a one-stop functionality because, with Issue Checklist, the items can include descriptions, mentions, due dates, and links.

as shown:

You can also create automation around these items to ensure that these requirements are met before an issue is transitioned.

Let me know if you need a tour of the App. Please reach out to us here.

[Summer Hogan]

Hi @Beth Shutt - Welcome to the community! 

As @Bill Sheboy described, I also use the story format in the issue description and then have sections in my user stories for the details about the requirements such as description, new fields, copy, etc. We also use the Smart Checklist for Jira Pro add on to track work that needs to happen and track progress. I have found that writing requirements in Confluence and linking those pages to Jira is a duplication of work. 

[Bill Sheboy]

Hi @Beth Shutt -- Welcome to the Atlassian Community!

Some of the smaller teams I have helped have done this, using a user story format in the issue description, and one of the marketplace addons for checklist fields. 

They put the acceptance criteria in the checklists, allowing both one-place-to-look for information and progress tracking as items are implemented.  This can also help if doing this as acceptance-test-driven work, using a GIVEN-WHEN-THEN format.  Perhaps try one of the free checklist addons first to see how that works, and upgrade if you want more features.

The comments (with mentions) helped when tracking changes from stakeholders during refinement, and prior to sprint planning / queue replenishment.

Kind regards,
Bill