How Detailed Should Acceptance Criteria Be in a Jira User Story?

[Balletrist]

A user story should stay focused on the user's goal, but developers still need enough detail to know when the work is actually complete. How specific do you make acceptance criteria without turning the story into a long technical specification? The template on the page separates the core user story from acceptance criteria, mockups, dependencies, and additional notes.

[Betsycrant]

I realize this is from a while ago, but I found your question really relevant. I've wrestled with the same balance. For me, keeping acceptance criteria focused on behavior rather than implementation helps. How do you decide what's essential versus over-specifying? I'd love to hear others' approaches too.

[charlimoun]

I found a practical balance by using a user story template for Jira that keeps the user goal front and center while tucking details like acceptance criteria and mockups into separate fields. That way, developers get the specifics they need without making the story itself feel like a spec. I have been using one like it myself, and it really helps the team know when work is done without losing focus.