Lesson 5 July 26th 2023

Lesson 5 Summary - AI Meeting Notes 

We have covered the following topics:

Scheduler Interior Automation: The meeting discussed how to automate repetitive actions in Jira using the scheduler interior automation feature. The process involves adding triggers, actions, and components to create rules that can be scheduled to run at specific times. The team will cover this topic in more detail during the next class.

Issue Types: During the meeting, the team explored issue types in Jira and how they work with each other. They looked at three levels of hierarchy - epic, story, and subtask - which are used for engineering projects by default. They also discussed customizing issue types by adding new ones or changing their names.

Fields and Screens: Another topic covered was fields and screens customization in Jira. Custom fields were created with multiple choice options such as department names for better organization of data entry forms. The team also explored advanced admin features that allow specifying requirements for custom fields such as where they appear on screens or who can edit them.

Overall, the meeting aimed to provide a deeper understanding of Jira's capabilities related to workflow automation through various features like scheduler interior automation while exploring different aspects like issue types hierarchy customization or field screen configuration options available within it so that everyone could make use of these tools effectively when working on their projects together

Custom Fields: The meeting discussed the creation and configuration of custom fields in Jira. Participants learned how to specify a custom field for a particular issue type or project, as well as how to group fields into different contexts. They also covered how to associate custom fields with screens and troubleshoot issues related to missing or misconfigured fields.

Collaboration: The meeting touched on collaboration between team members using Jira. Participants discussed sharing their screens during meetings, testing out new configurations together, and troubleshooting issues collaboratively using Jira's helper tools.

Technical Skills: Throughout the meeting, participants demonstrated technical skills related to working with Jira software. They navigated through various settings pages, created new issue types and projects, configured custom fields for specific contexts, associated those fields with screens in their projects' default screen schemes.

Issue Tracking: Another topic that came up was issue tracking within Jira software. Participants talked about creating new issues within their projects' issue type schemes and mapping them correctly so that all relevant information appears on each ticket's page when viewed by team members or stakeholders outside of the project team itself.

Project Management: Finally, participants discussed project management strategies using Jira software. They talked about setting up workflows for different types of tasks (e.g., spikes vs stories), assigning tickets to specific team members based on skill sets or availability levels at any given time during development cycles; monitoring progress through dashboards showing key metrics like burn-down rates over time; communicating updates via comments sections attached directly onto individual tickets themselves rather than relying solely upon email chains back-and-forth between multiple parties involved in each task being tracked by the system overall

Issue Configuration: Jerry explains that the department configuration page is not present in the screen configuration. He also shares an admin protip that clicking on blue links redirects to specific configuration pages, making it easier to configure fields.

Custom Fields: The meeting discusses different types of custom fields such as checkbox, date picker, number, text paragraph, radio button and multiple/single choice. They explain how values can be pre-filled for each field when creating an issue and how default values can be edited at any time. They also discuss disabling or deleting unused fields while keeping historical data intact.

Workflow Association: The team creates a new issue type called "Investigation" and associates it with a newly created workflow scheme with three steps - To Do, In Progress and Done. They map these statuses correctly in their project board settings by adding a QA column for testing purposes.

Break Time: After discussing the above topics for some time, they take a five-minute break before continuing further discussions on fixing fun things together later in the meeting.

Gira project admin settings: The meeting covered most of the Gira project admin settings, including configuration screens, workflows, and fields. The default system configuration is always in place but can be modified by creating a new field configuration scheme. Fields can be hidden or set to required from the field configurations or workflow transitions.

Creating a new field configuration scheme: To avoid affecting unintended projects, it's recommended to make a separate copy of the default field configurations and do changes on that copy instead. Once created, you can associate your new scheme with your project and configure which fields are required or hidden.

Hiding a Field: If you hide a particular field from your current setting using the test feature in Jira's administration panel, it will not appear anymore even if configured in screen schemes everywhere else. You can ask Jura where this problem is coming from so that you can fix it accordingly.

Understanding Jira configurations: The meeting discussed the different configurations in Jira, including fields, screens, screen schemes, issue type screen schemes, workflows and workflow schemes. These are all associated with a project and can be mapped to multiple workflows or field configurations. The team emphasized that understanding these complex mappings is crucial for effective use of Jira.

Simplifying Screen Configurations: One important aspect of configuring screens in Jira is simplification. By creating a new screen specifically for bug creation and editing it to only include necessary fields such as summary, issue type, component description priority labels attachments department etc., users can avoid confusion while filling out unnecessary information.

Issue Operations: Another configuration discussed was issue operations which include create view and edit options. It was noted that view and edit have been merged into one option in recent versions of Jira but separate screens can still be created for each operation if needed. This allows users to simplify the process by only showing necessary fields when creating an issue.

Mapping Screens with Operations: To associate an operation with a specific screen configuration in Jira project settings need to be adjusted accordingly by selecting the appropriate operation (create/edit/view) from the list provided under "Issue Operation" section then choosing which custom-made or default system-generated layout should appear on-screen when performing said action (e.g., creating bugs).

Creating and Testing Custom Fields: The team discussed creating custom fields in Jira to reduce noise and make it easier for end-users to fill out submission forms. They tested the custom fields for bugs, tasks, and stories. They also explored the "ad tab" feature that allows grouping of different types of fields together.

Project Settings Overview: The team reviewed project settings in Jira, including project details, issue types, workflows, screens and fields, versions, components roles and permissions notifications. They noted that mastering these features takes time but is essential for advanced modification.

Issue Subscription Notifications: The team briefly discussed issue subscription notifications in Jira. They mentioned receiving email notifications every 15 minutes until they disabled them due to spamming issues with their free account.

Homework Assignments: The team received homework assignments from previous lessons (parts one through three) as well as new homework assignments related to lesson five. These exercises are designed to help them practice using various features of Jira on their own time before the next meeting session on Monday.

Next Meeting Session Planning: Finally, the team planned for their next meeting session on Monday where they will have a more prolonged Q&A session over questions from homework assignments while learning a few more tricks on how to use Jira easily.