Acquisitions - Definition of Ready

Purpose: Story context for casual viewers.  What is this story supposed to cover?  If it's just an initial iteration of a larger feature, make that clear here.

User story statement(s): The user story statement is optional and you'll notice that many of our stories don't contain them.  This is because, between the purpose and the scenarios, there is usually more than enough information to go on.  That said, including a user story statement is best practice and if you have them please include them.  They will take the format: As a < type of user >, I want < some goal > so that < some reason >

Scenarios: On FOLIO, acceptance criteria are written as scenarios using the "gherkin syntax" (given, when, then)

Attachments/links: Whenever possible, a UX mockup should be attached or linked to the user story.  If there are elements of the mockup that are out of scope for the story (for example, because the technical prerequisites are not in place), then they should be noted as "out of scope for this story"  

Link Story to the related UXPROD feature.

Preformatted template for pasting into JIRA

*Purpose:*

*User story statement(s):*

As a < type of user >,

I want < some goal >

so that < some reason >

*Scenarios:*

#Scenario:

** Given <preconditions>

** When <actions>

** Then <results>

Overview: Optional high-level description of problem

Steps to Reproduce:

1. Log into some FOLIO environment as User X
2. Click this
3. Select that
4. etc.

Expected Results: What I expected to see happen

Actual Results: What actually happened

Additional Information: Anything else I noticed or tested that might be relevant to this issue

Interested Parties: Notify relevant people of this bug by @-mentioning them (type @ then search for their name).

Preformatted template for pasting into JIRA

*Overview:*

*Steps to Reproduce:*

# Log into some FOLIO environment as User X

# Click this

*Expected Results:*  

*Actual Results:*   

*Additional Information:*  

*Interested parties:*