Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Requirements, User Stories and Acceptance Criteria without Confluence

Beth Shutt
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 02, 2023

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!


4 answers

2 votes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 02, 2023

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. 

1 vote
Oleksandr Siryi_Railsware_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Nov 06, 2023

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. 

Screenshot 2023-11-06 at 9.15.16 AM.png

1 vote
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 04, 2023

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.

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 02, 2023

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,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events