Lesson 7 August 3rd 2023

Lesson 7 Summary - AI Meeting Notes 

We have covered the following topics:


System Settings: The meeting focused on exploring more of the system settings, specifically product access and different types of Jira admins such as project admin, board admin, and product admin. Speaker_1 emphasized that it's important to add users into the right groups where they have access to at least one of your products; otherwise, they will not see anything.

Project Administration: The group discussed project administration rights within team-managed projects versus board-managed projects versus global permissions schemes for multiple projects. Speaker_1 explained that each project has its own permission scheme which defines what you can or cannot do within a project based on user roles defined in that scheme.

Collaboration Tools: There was no discussion about collaboration tools during this meeting transcript

Jira Admin Hierarchy: The speaker explains the different levels of Jira admins, including Product Admin, Jira Site Admin, and Org Admin. They highlight the differences between each level and recommend limiting access to only a few individuals.

System Settings: The speaker walks through the General Configuration settings in Jira's System section. They explain how to change product titles, language settings, time zones, voting options for users on issues and more. 

Audit Log: The speaker discusses how to use Audit Log in Automation as well as its usefulness for monitoring activities related to Jira administration. They explain that it logs changes made by admins such as permission settings or group management.

Project Roles: The speaker explains how project roles are defined globally in Jira's Project Rules section. They suggest adding default members for each role so that new users can be easily added with appropriate permissions across all projects.

Supporting Details:

In terms of hierarchy within a company's use of Atlassian's software suite (JIRA), there are three main types of administrators - Product Administrator (or "JIRA Administrator"), Site Administrator ("JIRA Site Administrator"), and Organization Administrators ("Org admin"). Each has varying degrees of access rights within an instance depending on their role.


Within General Configuration under Systems Settings you can change your product title from 'JIRA' if desired; edit email templates sent from your instance; choose indexing languages; set up translations; select time zone preferences which will affect logging times throughout your instance.

Audit log is useful because it logs activities related specifically to administration tasks like permission changes or group management rather than every single action taken by users.

Project roles allow you define horizontal/vertical roles within a company using default groups attached/mapped together so when someone joins they just need their role defined once instead of having multiple configurations done across various projects individually.

Global Permissions: The speaker explains the global juror permissions and how to define them for anyone joining the Jira instance. They discuss who can administer the era, browse through projects and groups, see shared dashboards and filters, manage filter subscriptions, and make bulk changes. The settings are defined in Product Admin under each group's actions.

Issue Collectors: The speaker defines issue collectors as external collectors that collect issues from different types of applications. They recommend using Edons instead of external collectors because it is more user-friendly.

Global Automation: This topic covers where automation is set up in Jira's system settings. There is nothing new to see here that hasn't been covered so far.

Default User Preferences: This topic discusses two main things - outgoing email format and default sharing for filters and dashboards. By default, every time a user creates a new filter or dashboard it will be private unless changed by an admin.

Default Dashboard: The speaker explains how admins can set up a default dashboard for all users when they access their Jira instance. Users can also create their own custom dashboards but this sets the standard view upon login.

Branding Your Instance: In this section, they discuss changing your logo icon color scheme navigation color scheme etc., making your instance unique to your brand identity. 

Backup Manager & External System Import/Export:: These topics cover backing up data on cloud instances as well as moving issues between projects or instances using import/export tools provided by JIRA

Exporting and Importing Issues:
The speaker explains how to export and import issues in Jira using CSV files. They recommend exporting all fields, including custom fields, for easy importing. The speaker also demonstrates how to map the fields during the import process.

Atlassian Marketplace:

The speaker introduces the Atlassian Marketplace as a place where users can find apps that integrate with Jira. They advise users to check if an app is certified by Atlassian before installing it and to read reviews from other users.

Time in Status App:

The speaker recommends the Time in Status app from the Atlassian Marketplace as a useful tool for tracking how long an issue stays in each status. They guide listeners through installing and setting up this app on their own Jira instance.

App Management: The speaker explains how to manage apps in the system, including navigating to timing status and configuration pages. They also mention the ability to install and uninstall apps. The speaker highlights that it is essential to understand how each tool works before using it.

Tool for Tracking Issues: The speaker introduces a tool that tracks issues' time spent in different statuses, such as "to do," "in progress," or "ready for production." They explain how this tool can help identify potential bottlenecks and set KPIs for issue resolution times. Additionally, they discuss various settings available within the tool, such as filtering and sorting.

Github Integration: The speaker talks about integrating Github with Jira so that every time someone commits code with a Jira issue key in the build or branch name, information gets reflected on each ticket's development section. This integration helps visualize commits, pull requests builds without needing access to any repositories.

AI-Based Estimation Tool: A participant asks if there is an application that can help teams estimate story points when developers cannot estimate them accurately. The speaker suggests creating an AI-based estimation tool trained on existing data from previous estimations but cautions against relying solely on statistics since software development involves complexity where not everything can be predicted accurately.

Agile Methodology: The speaker suggests that for a team of juniors, it is better to ask them to create their own benchmark rather than imposing one on them. They can evolve and grow as professionals over time, and the evaluation scoring will change accordingly. The speaker also recommends creating a matrix based on complexity, uncertainty, and effort for each point.

Jira Issue Layout: The speaker explains the new functionality introduced by Jira called "New Issue Layout." It allows users to choose the layout through screens or project boards themselves. Users can configure what they see in this view or remove fields that are not needed.

View as User: This feature is mainly for Jira admins who can log in instead of a user facing issues with permissions or notifications. They can test out configuration changes from the user's perspective and troubleshoot any questions or issues faced by users.

Schedule Management: There is an issue with booking rooms until 4 pm due to another booking after that time. However, there are no other problems discussed regarding schedule management during this meeting.

Homework Submission & Feedback: No new homework will be assigned today; however, students should submit any queries by August 10th so they may be addressed before class resumes next week. Video snippets explaining each step of previous homework assignments will be shared by August 5th so students may compare their work against it before submitting questions if necessary.