Key Points

1. Jira has server and cloud versions
2. cloud version has limited flexibility and no update controls
3. role based permissions are global or by project

References

Key Concepts

Create custom Scrum boards as needed

Copy a default scrum board

create ticket stages that show on the scrum board

manage the tickets in backlog

when known, set the ticket release version

JQL - JIRA  Query Language

use JQL to get highly customized queries

every Search defaults to a text query not a JQL query

switch to advanced mode or JQL after text query runs

After a JQL query completes, there is an export option to a csv file that includes ALL columns on a work ticket

Working with the downloaded csv allows more flexibility in sorting, viewing stories etc

All maintenance on stories, epics, bugs etc should be done directly in JIRA vs attempts to import that updated stories

JIRA  product versions 

Server 

1. server versions on are managed on-premise and provide full control over add-in features, version upgrades etc for enterprise RAS

Core Cloud 

https://confluence.atlassian.com/jiracorecloud/jira-core-cloud-documentation-765593058.html

1. cloud versions do not provide any control on version upgrades issued by the vendor

Software Cloud 

https://confluence.atlassian.com/jirasoftwarecloud/jira-software-documentation-764477791.html

1. cloud versions do not provide any control on version upgrades issued by the vendor

Jira permissions made simple

https://confluence.atlassian.com/jirakb/permissions-made-simple-for-jira-server-717062767.html

The main concepts of JIRA permissions revolve around:  Users, Groups,  Global Permissions, Permission Schemes, and Project Roles. 

• Users are defined by having 'JIRA Users' global permissions. They can login and count towards your JIRA license. 
• Groups   are multiple users within your instance that need the same application permissions.
• Global Permissions   are system wide and are granted to groups of users. In JIRA we have the following permissions:
  • JIRA Administrators
  • JIRA Users
  • Browse Users
  • Create Shared Objects
  • Manage Group Filter Subscriptions
  • Bulk Change
• Permission Schemes   is a set of users groups or project roles assignments for the project permissions. A single JIRA project can only have one permission scheme. However, a particular permission scheme can be used by a number of projects. 
• Project Roles are a flexible way to associate users and/or groups with particular projects. Their main difference with JIRA groups is that they are  project-specific while groups are global across the JIRA application. 

Permissions Solution

The graph below illustrates Atlassian's suggested best practice when it comes to permissions.  

1. Only Project Roles are assigned to the Permission Scheme. Users and groups are not included in this phase.
2. Assign Project Roles to the users or groups through the project administration page.

By using the above set up you'll be able to re-use the same permission scheme for different projects and avoid duplication. 

Project Roles Main Players

In JIRA, we have three default roles namely: Administrators, Developers, and Users. 

Administrators

It contains the user/s who administer a given project in your JIRA application. They can add new users or groups, and manage components and versions as well.

Developers

It has the user/s who work on issues in a given project. They can be issues assignees and can edit, and log work on those issues.

Users

It contains people who create issues in a given project. They can view and comment on the issues they raised. 

Permission Schemes

For associating a permission scheme with a project, you can refer to this: Associating a Permission Scheme with a Project.

Further Readings 

• Managing Global Permissions
• Managing Project Roles
• Managing users and groups

Potential Value Opportunities

Organizing Client Work in Jira

Registered Users can Work in JIRA

Registered Users are billed for and can login to JIRA, perform work

Unregistered Users can't do anything in Jira BUT could view a project IF the admin setup to allow anonymous user access

Organizing Multiple Client Projects

create separate projects normally

if they are small, can create epics instead

For concurrent projects that have dependencies, SAFE practices are used to manage them ( Scaled Agile Framework )

Jira work hierarchy

Project > Epics > Stories > Tasks

All items can be customized

Multiple types of dependencies can be set between projects

Projects

Epics

Stories 

Tasks

Jira default workflows

Jira custom workflows

Key Focus Points

Common Roles in a Project 

Analyst

Designer

Developer

QA

Admin

Sprint Phases:   Preparation > Planning > Delivery > Review ( Demo, Retrospective )

Assign People to Roles

Scrum view << for Agile delivery where work is sequenced based on delivery dates, dependencies and capacity may vary to meet demand in some cases

Kanban view << used typically for maintenance work where capacity fixed and queue managed in priority order

Custom Dashboards

PM builds the backlog

PM defines the workflow if needed

PM defines the Definition of Ready for the Project

PM defines the Definition of Done for the Project

PM works with Planning Poker to pull work estimates from teams

Potential Challenges

Candidate Solutions

Step-by-step guide for Example

sample code block

Recommended Next Steps

Related articles