Jira
Use all basic types of tickets in Jira: Epic, Story, Task, Subtask, Bug.
Epic: page, big functional block, additional subproject
Story: user story and acceptance criteria (Gherkin format)
Task: general tasks (Team collaboration, setup the project, estimation, investigation, deploy, server tasks, etc)
Subtask: criteria of user story or additional subtask for team member
Bug: info of mistake with steps to reproduce and link to the Scope in confluence
Confluence
Add to space of the project Scope page as a shortcut.
Scope includes: Big functional section → Epic → Story and acceptance criteria
Epic in confluence
-
General info – general description of the epic in any form
-
Link to Epic ticket
-
Links to User story tickets
-
Visual design – files or links
Story in confluence
-
General info – general description of the User story in any form (may include additional context of the task)
-
User story (feature)
-
Visual design – Design files or links to them, other additional links (email templates, API documentation, etc.)
-
Acceptance criteria Gherkin (Given, When, Then) in a table view, where the first column is the numbering of the criteria, the second column is the scenario, the third column is a screenshot from the design or Wireframe of how it should look (not the way it is now, but how it should be).
Gherkin format
User story (feature)
-
Given: context, page where to log in
-
When: some event or user action
-
Then: what we get as a result
-
AND: if you need to add/get several scenarios, actions, results
Bug report
-
Actual result: text description of the bug reproduction
-
Expected result: text description of how it should work (link to the page with Acceptance criteria)




Leave a Reply
You must be logged in to post a comment.