Implementers is hoping to get the word out about the need for a new PO for Locations and Service Points, as well as a convener for Courses.
Tara also mentions that this fall, she will start asking for volunteers for the Implementers Convener slot for 2024.
04:46
Release Notes Redesign Feedback
Khalilah asked that we look at the Release Notes Redesign Board and provide feedback. Tara posted about this on slack, but you can add feedback directly to the board.
05:31
Using Jira for Implementers
Julie has come to explain Jira to us!
Her plan is to start by explaining what Jira is used for in the FOLIO project, then explain how Jira is organized, and then explain how users from implementing libraries can best make use of Jira.
07:22
What is Jira used for?
Jira is a communication tool between the people who are working to get FOLIO developed and the people who need specific functionality in FOLIO. End users (most of us) communicate with the Dev Team (POs, programmers, QA...) who also communicate with the Release Team.
End users typically use Jira to provide or find information--we tend not to actually work on issues.
(09:20) Jira is also a repository of "tickets." (Tickets are properly called "issues" in Jira, but most people use these terms interchangeably.) These tickets have descriptions and fields that help to explain what is currently happening, and what will happen in the future. It's a living, growing story about the work being done.
12:01
How is Jira organized?
Jira is organized into many different types of tickets, using terminology and concepts from Agile methodology. We go over the main ones, and we discuss the definitions of the main fields in each type of issue:
Epic (12:10): work that represents several releases, or continuous work.
Feature (16:00): Represents a work increment this is relevantly self-contained. It may be new development or non-functional requirements, like accessibility or performance issues. This is typically the level of organization most interesting to implementers--it represents an actual piece of functionality we want to see. Features are always in the UXPROD project in Jira.
20:51
Jira tips and questions
(20:51) Watching issues--you can add yourself as a watcher on issues you want to track.
(22:34) Any user can comment on a ticket. You can do this to express interest, ask a question, or add information. You can also find POs on slack and ask questions there.
(24:04) For the most part you should not be changing fields on issues that aren't yours, but labels are the exception--feel free to add labels to help you find issues in whatever way you need. (Do not delete labels!)
(25:20) Votes and ranking are no longer used in Jira--interest is expressed in other ways.
(26:06) David asks if the FOLIO project uses Jira Service Management. We do not. For the most part, POs create tickets themselves--this is important because the requirements for refinement are so specific.
32:10
How is Jira organized? Part 2
We continue our discussion of the different types of tickets.
Story(32:18): Represents work to be done in one sprint. This is the level that programmers work on. Unlike features, information is stored in many different projects, which are linked to the names of the modules.
Other types of issues include bugs, tasks, and tech debt (38:10)
Bugs are a very important one for Implementers. Bugs are typically linked to features, and they generally include a templated write-up of the problem. IMPORTANT: to get your important bugs looked at, label them "support" to get the support sig on it.
Tasks: this that need to be done that do not require code.
Almost all end users will at some point need to search for issues. There is both an advanced and basic search.
Julie demos some of the basic features that allow searching and filtering. (45:43) Power users will find Jira's advanced querying with JQL especially useful.
You can also save filters you use often (46:30), and create dashboards based on your filters. (47:08)
You can also browse public boards created by others.
Mentioned throughout our meeting–implementers are welcome to add comments!
52:40
Questions
Tara asks: can end users submit bugs? Julie says yes, but it's important for the bugs to be created in the correct project, described in a specific way, and reproduced in the appropriate environments. For this reason, it's important to either tag the PO so they see it, or ask the PO to create the bug in the right way. Users should write the description--what is the problem, what are the steps to reproduce, and where did you see it.
56:03
Thanks Julie!
We say thank you to Julie, who reiterates that we can reach out to her on slack with questions about Jira any time.