To effectively use a ticketing system, I should practice logging tickets, assigning them, troubleshooting issues, documenting resolutions, and analyzing reports. My best practices include clear communication, prioritization, thorough documentation, and leveraging automation to improve efficiency and enhance user satisfaction.
- Kanban board focuses on continuous work flow without the constraint of sprints and is often used for teams managing ongoing tasks, bug fixes, or support tickets.
- Scrum board is designed around sprints and includes sprint planning, sprint backlogs, and burndown charts to track progress.
- Navigating your project inside of Jira
- Learned how to create epics, user stories, bugs, and subtasks in into backlog
- Assigning epics to issues
- Use releases to track versions in the project
- Grooming the backlog, what features must be they have so the product can be used by the users
- Cleaning up the backlog, is every issue assigned to an epic
- Setting up a sprint and generating a sprint graph
- Jira
Ref 1: Creating a homelab for hands-on experience on using Jira Ticket System
Ref 2: Creating a project for E-Commerce software application using the Scrum method
Ref 3: Officially created a Scrum for the E-Commerence software application on Jira
Ref 4: Using the backlog to create issues for our epics for our issues, stories and bugs
Ref 5: E-Commerce Shopping Software App Epics
Ref 6: E-Commerce Shopping Software App Epics > User Stories > Tasks > Sub-tasks > Bugs
Ref 7: Creating an Epic in our backlog, naming the summary as Shopping Cart and giving it a description
Ref 8: If the epic doesn't show up on your backlog, make sure that the dropdown list is set to epic
Ref 9: On the drop down arrow next to Epic, you can change the details
Ref 10: Creating Epics for Cancelling Orders, User Account, Shopping Interface, Product Search, Loyalities Programs, and Shopping Locations
Ref 11: Creating a user story on Jira for shopping cart epic
Ref 12: Once the story was created it shows up as a backlog under the shopping cart epic.
Ref 13: Creating another story with the shortcut of clicking the "+" button belong the backlog box. It's a quick way of adding stories but need to go back to add the epic it belongs to at a later time
Ref 14: Creating several entries for Bugs to be fixed
Ref 15: Click Add > Child issue > input what needs to be done for subtask
Ref 16: Now we go back to the logs to assign Epics to the stories. You can click and drag them to their appropiate epics or click the boxes to the left of the stories if you need to drag multiple to the same epic
Ref 17: Creating labels for each epic so they're catgorized seperately. Shopping cart, cancelling orders, shopping interface and product search gets the "shopping" label. User account and loyalities gets "user-admin" and shopping location gets "shop-info"
Ref 18: Create Version, enter the information required for the field for name, start and end date, and description. If you're having a hard time finding the release tap, click on add view > more features > check if the "release" tap option is enabled
Ref 19: Enable version on the drop down menu
Ref 20: Dragging related epics to version 1
Ref 21: Creating Version 2.0 and adding user accounts and product searches to it
Ref 22: Creating Version 3 and doing the same as before for the last two epics loyalties program and shopping location interface
Ref 23: Drag and drop the issues in the backlog above or below the appropriate issue, so it's ranked and prioritized appropriately. Priortize issues UPWARD. Compare issues to those above it, and prioritize it accordingly. This is grooming the backlog.
Ref 24: An example of grooming the backlog, by prioritizing items on top over the ones on the bottom
Ref 25: Filtering issues without epics, makes sure that all features aligns with the project goal
Ref 26: Click on the "create sprint" button to make a new sprint for the project
Ref 27: This is where "story points" comes into play. The lower the number the simpler the task is and vice versa, the higher the number the more difficult and time consuming it is
Ref 28: In this senario the epics have been assigned their story points and have reached the maximum amount, 34, to be completed within a two week period
Ref 29: Checked boxes on epics with scores and the bugs and dragged them into the sprint box
Ref 30: Assigning each task in the sprint to myself, for the example. In reality, its best to assign a few task to each member of the team to reduce the work load
Ref 31: Click the "start sprint" button to start it. From there we change the duration to custom, in real life situation its normal to have it set at 2 weeks, start and end date would be 1/30/25 with a 45 minute time limit
Ref 32: A sample Sprint broad has been generated for us with three columns; to do, in progress and done. Normally in real life situation you'll want to customize the sprint depending on the project
Ref 33: Three dots on the top right, click configure board
Ref 34: Added a fourth column "verify". At first there was only three status available so you need to create a new one for verify in order to save the changes. Click on manage workflow to add "verify" workflow
Ref 35: Example of how the board would look like w/ the task in eithe of the columns
Ref 36: Pull up the reports overview tab and click on sprint burndown chart. In a real world cases, this graph would be different but for demonstation purposes to see what its like to move the stories through the columns from to do to done
