Jira administration Trantor
Download as PPTX, PDF0 likes92 views
This document provides an overview of key Jira administration topics including workflows, screens, custom fields, permissions, and boards. It discusses how workflows define issue statuses and transitions, the different types of screens used to represent data, how custom fields store additional values, how project and global permissions are managed, and how Kanban and Scrum boards can be used with different methodologies. The document aims to explain the basic concepts and functionality for administering a Jira system.
Jira administration Trantor
- 1. Jira Administration Presented By: Maitrey Patel 13th August 2021
- 2. Index Workflows Screens Custom Fields Project & Global Permissions Kanban & Scrum boards Versions & Components
- 3. Workflows • A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle and typically represents processes within your organization. • Options to use while transitioning the issue: • Properties • Conditions • Validators • Post Functions
- 4. Screens Visual Representation of the data. Types of Screens Create View Edit Transition Not adding field to the Edit screen will prevent users to Edit/Update the field values. Use cases: Set value one time either at creation or at transition.
- 5. Custom Fields • Placeholders to store values. • Basic types of fields: • Textbox (Single Line / Multiline) • Select List(Single/Multi Choice / Cascading) • Radio Buttons • User Picker (Single / Multiple) • Checkboxes • Data / DateTime picker • Number Field
- 6. Project & Global Permissions • Project permissions can be managed by project administrators only if permission scheme is dedicated to only one project. • These permissions are specifically to the project that includes: • Issue/Ticket • Comments • Attachments • Time Tracking • Global permissions are managed by Jira Administrators. • Global permissions are as follows: • Browse Users • Create Shared Objects (Dashboards, Filters) • Manage group filter subscription • Bulk Change
- 7. Kanban & Scrum Boards • Any Jira Software project may have multiple boards in combination with Kanban and Scrum. • Kanban is generally used for the support teams as they don’t have roadmap. • Kanban doesn’t have sprint. • Scrum follows the full agile methodology. • Scrum board has sprints and sprint planning. • Scrum suites the software development team who follows the agile methodology.
- 8. Version & Components • In Jira Software, versions help you organize your work by giving you milestones to aim for. You can assign issues in your project to a specific version and organize your sprints around completing work in that version. • Fix Version, Affected Version • Jira project components are generic containers for issues. Components can have Component Leads: people who are automatically assigned issues with that component. Components add some structure to projects, breaking it up into features, teams, modules, subprojects, and more.
- 9. Q & A