What are Jira Software Issues: An Overview of Tasks, Bugs, Stories, and Epics
Вставка
- Опубліковано 2 сер 2024
- 80% off - UDEMY COURSE - Atlassian Jira and Scrum Fundamentals for Beginners: go.vlkedu.com/jira-scrum-fund...
80% off - UDEMY COURSE - Practical Jira workflows and Boards:
go.vlkedu.com/jira-boards-wor...
80% off - UDEMY COURSE - Atlassian Confluence Fundamentals for Beginners: go.vlkedu.com/confluence-fund...
A comprehensive overview of the different Jira issue types, including Stories, Tasks, Bugs, and Epics, and how to effectively manage them within the Jira platform.
If you are somewhat new to Jira and you see the term ‘issue’ or ‘issues’ on many Jira screens, you might be wondering what Jira issues are, what are different issue types, how to use them, and what are Jira tickets.
In this video, I will explain Jira issues (or tickets, which is the same thing) using many examples. I will review all issue types and their purpose and show you how to create and manage Jira issues.
After watching the video, you will be able to apply the learnings to your own work, identify the correct issue type for your own situation, create issues in Jira, and process them through different work stages.
This video is primarily intended for beginner and intermediate Jira users, but the concepts discussed are applicable for any proficiency level, and watching it will likely be worthwhile.
My name is Vlajko Knezic and thank you for watching this video.
---------------------------------------------------------------SUBSCRIBE TO MY UA-cam CHANNEL:
- / vlkedu
VISIT MY WEBSITE:
- vlkedu.com
New to Jira or Confluence? Check my high ranking Jira and Confluence beginners courses on Udemy!
80% off - Practical Jira Workflows and Boards for Scrum Projects: go.vlkedu.com/jira-boards-wor...
80% off -Atlassian Jira and Scrum Fundamentals for Beginners: go.vlkedu.com/jira-scrum-fund...
80% off - Atlassian Confluence Fundamentals for Beginners: go.vlkedu.com/confluence-fund...
Odlicno Profesore! Hvala na vasoj pomoci!
wow. fantastic overview and presentation!
Watched 10 other videos trying to find the information presented like this. Thanks so much, super helpful
Great to hear that, thanks!
Extremely well said!
Legend 👏 love this!!!
Great video! Thank you!!
Thanks for this!
Thank you for making this topic so much easier to understand.
Glad it was helpful!
The examples provided were very useful for beginners. Hard to find a video like this one, thanks!
I'm glad you liked the examples! You're welcome!
Great presentation. Clear!
Thank you!
Glad you enjoyed it!
Great explanation. thanks !
Glad you liked it
Very useful thank you!
You're welcome!
The best explanation available
Glad it was helpful!
Thanks 😊
You're welcome!
Thanks
No problem
Nice but with some notes, I would like to discuss with you how I manage my team with jira, for user stories I use a template ( as a.... I want to.... So that.... Given that....) also I split each user story into tasks ( front end, back-end, mobile) and each developer breaks his task into sub-task, once all tasks are moved to done, the user story is considered to be done, this way I can track user stories and measure project overall progress
Thanks for the feedback. This can be a long topic to discuss, but here is a brief summary.
As a .. I want to ... etc is one of the formats to right a user story but certainly not the only one. There is no single right way to right story, and as long as stories are written as "an informal, general explanation of a software feature written from the perspective of the end user or customer", and a format works for the product owner and developers, such format is acceptable.
User story should not be broken into tasks because tasks represent the same level of functionality as story but a different nature (generally something that is not a product feature). Subtasks should be used to break down stories and tasks if necessary, but it is not mandatory. More mature Scrum or Kanban teams would generally not use subtasks.
Lastly, a story should be considered Done only when accepted by Product Owner. It is possible to have situations when all subtasks are completed but story is not accepted by PO in which case that story should not be considered Done. Reverse is also possible - PO has the authority to mark a story Done even when there are incomplete related subtasks.
You should add Testing swimlane after in progress
Hey, what about the QA work? where would they be allocated? as a task? within an user story? thanks!!
QA work is usually captured using sub-tasks. In general, subtasks can be used to break down any of your standard issues in Jira (bugs, stories, or tasks). That would ensure that all work required to complete a story (or a bug, or a task) is captured in the context of a story (or a bug, or a task). Besides QA work, sub tasks might include coding work, design work or anything else the team thinks should be captured. It is up to the team to decide how granular they want to be.
why is there a VERY LOUD sound in the beginning compared to the voice of the presenter?