The following is from JIRA:
User stories are sketched out by the product owner, then the full product team collectively decide the more detailed requirements.
These are the granular pieces of work that help define the implementation items for the story and the upcoming sprint. In the above example, there are a set of tasks required to make the account feature work: database changes, new server logic, as well as new user interface components. These tasks should be fleshed out during estimation of the user story and linked in the team's issue tracker.
But I thought User Stories were written out like As a <type of user>, I want <goal> so that I <receive benefit>. I am a bit confused, where do I write the granularity (the lower-level individual tasks that are associated with developing the item listed in the User Story).
Also, do we not use acceptance criteria in JIRA?