Built-in Jira Software Reports

Jira comes with many built-in reports to provide insights into progress, release health, time logged, forecasts, and more. Each Jira application type, deployment type and project type contain different reports however. I’ve compiled a list of the report types and their definitions in Jira Software, so you don’t have to!

Tip: Be sure to consider reporting options when choosing between project types.

Sections: Jira Software: Cloud | Company-managed Scrum Project |
Company-managed Kanban Project | Team-managed Scrum Project |
Team-managed Kanban Project | Jira Software: Server and Data Center |
Scrum Project | Kanban Project | Extending Reporting Capabilities

Jira Software: Cloud

Company-managed Scrum Project

Report count: 23
Unique reports: Cycle Time Report, Deployment Frequency Report, and Workload Pie Chart Report

Agile

  • Burndown Chart – Track the total work remaining and project the likelihood of achieving the sprint goal. This helps your team manage its progress and respond accordingly.
  • Burnup Chart – Track the total scope independently from the total work done. This helps your team manage its progress and better understand the effect of scope change.
  • Sprint Report – Understand the work completed or pushed back to the backlog in each sprint. This helps you determine if your team is overcommitting or if there is excessive scope creep.
  • Velocity Chart – Track the amount of work completed from sprint to sprint. This helps you determine your team’s velocity and estimate the work your team can realistically achieve in future sprints.
  • Cumulative Flow Diagram – Shows the statuses of issues over time. This helps you identify potential bottlenecks that need to be investigated.
  • Version Report – Track the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind.
  • Epic Report – Understand the progress towards completing an epic over time. This helps you manage your team’s progress by tracking the remaining incomplete/unestimated work.
  • Control Chart – Shows the cycle time for your product, version or sprint. This helps you identify whether data from the current process can be used to determine future performance.
  • Epic Burndown – Track the projected number of sprints required to complete the epic (optimized for Scrum). This helps you monitor whether the epic will release on time, so you can take action if work is falling behind.
  • Release Burndown – Track the projected release date for a version (optimized for Scrum). This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

DevOps

  • Cycle Time Report– Understand how much time it takes to ship issues through the deployment pipeline and how to deal with outliers.
  • Deployment Frequency Report – Understand your deployment frequency to understand risk and how often you are shipping value to your customers.

Issue analysis

  • Average Age Report – Shows the average age of unresolved issues for a project or filter. This helps you see whether your backlog is being kept up to date.
  • Created vs. Resolved Issues Report – Maps created issues versus resolved issues over a period of time. This can help you understand whether your overall backlog is growing or shrinking.
  • Pie Chart Report – Shows a pie chart of issues for a project/filter grouped by a specified field. This helps you see the breakdown of a set of issues, at a glance.
  • Recently Created Issues Report – Shows the number of issues created over a period of time for a project/filter, and how many were resolved. This helps you understand if your team is keeping up with incoming work.
  • Resolution Time Report – Shows the length of time taken to resolve a set of issues for a project/filter. This helps you identify trends and incidents that you can investigate further.
  • Single Level Group By Report – Shows issues grouped by a particular field for a filter. This helps you group search results by a field and see the overall status of each group.
  • Time Since Issues Report – For a date field and project/filter, maps the issues against the date that the field was set. This can help you track how many issues were created, updated, etc, over a period of time.

Forecast & management

  • Time Tracking Report – Shows the original and current time estimates for issues in the current project. This can help you determine whether work is on track for those issues.
  • User Workload Report – Shows the time estimates for all unresolved issues assigned to a user across projects. This helps you understand the user’s workload better.
  • Version Workload Report – Shows the time estimates for all unresolved issues assigned to a version, broken down by user and issues. This helps you understand the remaining work for the version.

Other

  • Workload Pie Chart Report – A report showing the issues for a project or filter as a pie chart.

Company-managed Kanban Project

Report count: 15

Agile

  • Cumulative Flow Diagram – Shows the statuses of issues over time. This helps you identify potential bottlenecks that need to be investigated.
  • Control Chart – Shows the cycle time for your product, version or sprint. This helps you identify whether data from the current process can be used to determine future performance.

DevOps

  • Cycle Time Report – Understand how much time it takes to ship issues through the deployment pipeline and how to deal with outliers.
  • Deployment Frequency Report – Understand your deployment frequency to understand risk and how often you are shipping value to your customers.

Issue analysis

  • Average Age Report – Shows the average age of unresolved issues for a project or filter. This helps you see whether your backlog is being kept up to date.
  • Created vs. Resolved – Issues ReportMaps created issues versus resolved issues over a period of time. This can help you understand whether your overall backlog is growing or shrinking.
  • Pie Chart Report – Shows a pie chart of issues for a project/filter grouped by a specified field. This helps you see the breakdown of a set of issues, at a glance.
  • Recently Created Issues Report – Shows the number of issues created over a period of time for a project/filter, and how many were resolved. This helps you understand if your team is keeping up with incoming work.
  • Resolution Time Report – Shows the length of time taken to resolve a set of issues for a project/filter. This helps you identify trends and incidents that you can investigate further.
  • Single Level Group By Report – Shows issues grouped by a particular field for a filter. This helps you group search results by a field and see the overall status of each group.
  • Time Since Issues Report – For a date field and project/filter, maps the issues against the date that the field was set. This can help you track how many issues were created, updated, etc, over a period of time.

Forecast & management

  • Time Tracking Report – Shows the original and current time estimates for issues in the current project. This can help you determine whether work is on track for those issues.
  • User Workload Report – Shows the time estimates for all unresolved issues assigned to a user across projects. This helps you understand the user’s workload better.
  • Version Workload Report – Shows the time estimates for all unresolved issues assigned to a version, broken down by user and issues. This helps you understand the remaining work for the version.

Other

  • Workload Pie Chart Report – A report showing the issues for a project or filter as a pie chart.

Team-managed Scrum Project

Note: Application and project administrators need to enable this feature at: Project Settings > Features.  See screenshot

  • Burnup report – Visualize a sprint’s completed work and compare it with its total scope. Use these insights to track progress toward sprint completion.
  • Sprint burndown chart – Track and manage the total work remaining within a sprint. After the sprint, summarize both team and individual performance.
  • Velocity report – Predict the amount of work your team can commit to in future sprints by seeing and reviewing the amount of value delivered in previous ones.
    • Note: A completed sprint is required
  • Cumulative flow diagram – Shows the statuses of your project’s issues over time. See which columns accumulate more issues, and identify bottlenecks in your workflow.
  • Cycle Time Report – Understand how much time it takes to ship issues through the deployment pipeline and how to deal with outliers.
  • Deployment Frequency Report – Understand your deployment frequency to understand risk and how often you are shipping value to your customers.

Team-managed Kanban Project

Note: Application and project administrators need to enable this feature at: Project Settings > Features.  See screenshot Additionally, some reports require sprints. Enable them on the features page too, if desired.

Same as the team-managed scrum project above.

Jira Software: Server and Data Center

Scrum Project

Same as the company-managed scrum project above without the following reports: Cycle Time Report, Deployment Frequency Report, and Workload Pie Chart Report

Kanban Project

Same as the company-managed kanban project above without the following reports: Cycle Time Report, Deployment Frequency Report, and Workload Pie Chart Report

Extending Reporting Capabilities

Most reports are customizable and if you can’t get to the data you’re after, there are plenty of apps available in the Atlassian Marketplace.

Choosing the right Jira project type

Jira has three application types and each is built for a specific audience and use. The types are: Jira Work Management (JWM), Jira Software (JS), and Jira Service Management (JSM). All three types have the same look and feel but different features. The applications can be used separately or together. For example, your organization might use Jira Work Management and Jira Software but not Jira Service Management.

Additionally, each Jira application type contains different project types. Each has special features not available in other project types. Here are the major differences and how to select the best project type for your team’s needs.

Project Types in Jira Cloud

Jira Work Management

Jira Work Management contains all the main Jira features like projects, issues, workflows, and users. You can think of it as providing the core functions of Jira. In fact, it was previously named “Jira Core”. Atlassian added some new and interesting features before renaming it in April 2021. This application type has business projects, templates, and features.

This project type is best for teams like marketing, finance, legal, sales, human resources, and more. Its commonly used for managing projects, processes, and tasks.

Jira Work Management is only available in Cloud and there are two plans: free and standard. Jira Work Management is included with every Jira Cloud license. In Jira Server, the application is still called Jira Core. In Jira Data Center, there’s no such application.

Business Project Features

Business projects in Jira Cloud have some additional views that aren’t available in other project types. The features noted below are fairly new and will continue to be improved over time.

List View

The list feature displays parent and child issues in a expandable list format. It’s similar to the format presented after searching or viewing filter results but there’s no JQL query to construct. Instead, all issues in the project are displayed and there’s an easy menu to filter issues by assignee, component, issue type, labels, priority, reporter, and status. You can also filter by issues “due this week”. This feature is a quick and easy way to view issues in a project without needing any query skills.

The best part of this view is that parent issues can be expanded or collapsed to show or hide child issues. This hierarchy capability is highly desired but missing in other areas of Jira. In the example screenshot, the task PMO-1 is expanded to show it has four sub-tasks.

List view in a Jira Cloud business project

Good to Know

The epic issue type does not display as part of the hierarchy in list view. I suspect that this is because epics are a software project concept, not a business project concept. Jira Cloud has many business templates, but none of them include the epic issue type by default. I manually added it to the sample project in the screenshot above because I like how epics help categorize work. To see an expandable view of epics and parent issues (but not child issues) use the roadmap feature in a software-type project.

Calendar VIEW

Jira Issues Calendar

Until now, the only way to view issues in calendar format was by adding the “Jira Issues Calendar” macro to a dashboard. The functionality is basic. Issues are displayed based on a Jira project (or JQL filter) and a single date field. The total number of issues associated with a specific day are summed.

In the screenshot, there’s one issue due on October 27 and one due on October 30. The colored boxes represent different workflow statuses. In Jira, hover over the colored boxes to see issue details or click the box to view individual issue details. Fix versions can also be displayed. Finally, you can also export the data to iCal format.

The new calendar view in Jira Cloud business projects is not part of a dashboard and includes some useful additions. The display accommodates start and end dates, assuming you utilize the standard Jira “start date” and “due date” fields. This view also shows the issue type, key, summary, and assignee. The filtering capabilities work the same as described in the “list” view.

Again, notice that parent and child issues are displayed but not epics.

Timeline VIEW

The timeline view is similar to the roadmap view in a software-type project. This display includes a Gantt-type chart where issues duration is represented by colored bars. Start dates, end dates, and assignees are displayed. Dependencies are created using the standard linked issues feature and indicated using curved red lines. (Not pictured.) The same filtering abilities in the other views are present as well.

Forms

The final new feature for business projects in Jira Cloud is forms. Use a form to collect additional information without adding new Jira issue types or custom fields. Currently, you can create one simple form per Jira business project. The form has a unique URL that can be shared with any licensed Jira user. A Jira issue is automatically created after any form submission.

Form configuration
Example form
Submission message
Submission result

Since the “forms” link in the project’s left sidebar menu is plural, I’m hoping that multiple forms are supported in the future.

Read more

License Differences

Jira Work Management users are not able to use agile or software development features in software projects or support features in service management projects. Access to business projects is available to all types of licensed Jira users. Read more

A JWM user license is less expensive than a JS user license. When choosing between application and project types, it’s important to compare pricing, project access, and feature differences.

See Atlassian’s JWM product page and the table on the pricing page for additional feature information.

Jira Software

The next application type is Jira Software. This type is designed for development teams. Although any software development methodology is supported (including Agile, waterfall, or even no methodology or framework) this project type caters to teams using Scrum or Kanban.

Jira Software is available in Cloud, Server, and Data Center. In Cloud, there are four plans: free, standard, premium, and enterprise.

Software Project Features

Jira Software includes the following additional development-specific features:

  • Project templates for Scrum, Kanban, and bug tracking
  • Scrum boards for teams that plan in chunks of work called “sprints”
  • Kanban boards, for teams with less structured delivery schedules
  • Sprints to manage iterations or scheduled work
  • Sprint capacity planning (in Jira Cloud Premium and Enterprise) to avoid over or under resource utilization
  • Story points for relative effort estimation (time-based estimation is also available)
  • Backlog functionality to help teams prioritize future work
  • Release tracking functionality to manage deployments
  • Fix versions to schedule work and affected versions to manage code changes
  • Release tracks (in Jira Cloud Premium and Enterprise) to manage when and how software changes are released
  • Roadmaps to view work in a Gantt-type format
  • Additional built-in reports to track burndown and burnup, velocity, epics, releases, and more
  • Integration with code and deployment tools like Bamboo, Bitbucket, and Opsgenie
  • And more

License Differences

Only Jira Software users can leverage development specific features.

See Atlassian’s JS product page and the table on the pricing page for additional feature information.

Learn more about the software development life cycle (SDLC) and using Atlassian applications to plan, develop, test, and release software with my Planning and Releasing Software with Jira course. (Coming soon!)

Jira Service Management

The final application type helps support teams of all types manage their requests.  Atlassian created JSM in 2013 after noticing that 40% of customers had adapted Jira to handle service requests.

JSM is for tracking changes to systems, processes, or applications, resolving incidents and problems like an outage or security breach, fulfilling service requests like a password reset, new hardware, or issuing a mobile device, managing approvals of all kinds, and helping internal or external customers with whatever they need.

Business teams can take advantage of JSM features too. For example,
the HR team can collect benefits questions and reimbursement requests, the facilities team can receive requests for new desks and chairs, and the legal team can process contract review requests.

Sometimes teams have more than one project like a service-type project to support their “customers” and another business-type project to manage all their internal “to do” items. For example, the finance team can have a service project that every employee has access to. This project is used to collect employee reimbursement and purchase requests. They can also have a business project that only finance team members have access to. This project is used for tracking team tasks like maintaining reports and adding new employees to the payroll system.

As always, keep the long term health of the application in mind by not creating more Jira projects, settings, and schemes than you truly need.

JSM is available in Cloud, Server, and Data Center. In Cloud, there are four plans: free, standard, premium, and enterprise. Jira Service Management was previously called Jira Service Desk.

Service Project Features

While you can certainly use other Jira application types for support, Jira Service Management takes support to the next level.

JSM includes the following additional support-specific features:

  • Project templates for ITSM, customer service, and other support type teams (in Jira Cloud)
  • Dedicated queues to organize and categorize requests (in addition to standard JQL filtering capabilities)
  • Request categories for segmenting service requests, changes, problems, and incidents (found in the Jira Cloud “IT service management” project template)
  • Service Level Agreements (SLAs) to define goals and measure metrics like response or completion time
  • A simple customer portal (aka “help center”) featuring a streamlined interface and slightly customizable display
  • Integration with Confluence as a self-service knowledge base
  • Asset and configuration management (in Jira Cloud Premium and Enterprise)
  • Built-in reports for tracking agent workload, customer feedback, and requests deflected by self-help articles
  • Better support for creating issues via email (and from non Jira users)
  • An embeddable widget (in JSM Cloud) to create issues from other web pages or applications
  • Customizable notifications for customers
  • Permission schemes allowing customer access
  • A simple customer survey to collect customer feedback (CSAT)
  • Integration with monitoring, alert, and notification tools like
    Opsgenie
  • The ability to automatically create issues in software projects from events in service projects without impacting automation rule execution limits
  • And more

License Differences

The licensing model is different in this application type. Jira Service Management has two additional types of users: agents and customers.

An agent is anyone providing support, managing the support team, or monitoring support team effectiveness. The agent is the technician who solves a problem or provides the requested help. An agent does all their work in Jira and requires a JSM license to use service features.

A customer is anyone who requests support. Customers can include internal users, external users, employees, vendors, contractors, and anyone else who needs help. Customers file support requests and view progress in a simplified interface called the customer portal or help center. Customers generally don’t access the area of Jira that agents use to fulfill requests.

See Atlassian’s JSM product page and the table on the pricing page for additional feature information.

Learn more about JSM users, features, and configuring support projects with my Jira Service Management: Administration course.

Bonus: Product Discovery

While I was taking screenshots, I noticed a new type on the projects page in Jira Cloud. The new type is called “project discovery” and it’s intended for product managers. Learn more about this new type and sign up for early access at: https://www.atlassian.com/software/jira/product-discovery

How to Choose a Project Type

As you can see, there’s a lot to consider when selecting a Jira application type and project type. While it’s easy to switch between Jira project types in Server and Data Center, it’s a more involved process in Cloud.

Potential reasons to choose a business project type:

  • Easier to use and navigate for less technical Jira users
  • Cheaper user license fees
  • All issue types can leverage the same workflow
  • The new list, calendar, and timeline views are easy to use and don’t require JQL
  • The forms feature is an interesting addition
  • The timeline feature provides a sufficient visual view

Potential reasons to choose a software project:

  • The primary users write, release, and deploy code, and/or use development tools like Bamboo or Bitbucket
  • Backlog, sprint, and/or Scrum board functionality is needed to prioritize and schedule work
  • Epics are used to categorize work
  • Multiple workflows are needed to manage different processes
    • Example: A bug’s workflow includes a verification step, a change request’s workflow includes an approval step, a task’s workflow includes neither.
  • Software users can access both software and business projects
  • The roadmaps feature is preferred over the timeline feature
  • There’s a desire to track metrics like burndown, burnup, and velocity

Potential reasons to choose a service management project:

  • The primary users provide service and support for products or applications, to other teams, or to internal or external customers
  • Requestors don’t have Jira licenses
  • Requestors are less technical users
  • There are deadlines (SLAs) to meet for specific requestors or certain types of requests
  • The team uses monitoring, alert, or ChatOps tools
    • Note: Other project types can integrate with Slack and Microsoft teams as well

Can you think of other reasons to choose a specific project type? Please add your thoughts in the comments section below.

Related Articles

For related information on the different types of Jira and changes over the years, please see:

Jira Automation Ideas

In case you need some inspiration, here are 65 ways you can use automation in Jira to make your life easier. You can accomplish all of these with built-in automation, workflow extensions, and scheduling apps!

Communicate Information

Send additional notifications

  • Notify the project manager when an initiative is approved
  • Notify customers when their feedback or bug is addressed
  • Alert the legal and customer service teams when a new product launches
  • Use an integration or a webhook to notify your team’s chat room of certain Jira events

Send weekly updates

  • Send a report of all the issues you worked on this week

Show instructions

  • Provide an on-screen message, after a workflow transition, to remind a user to perform a task they frequently forget to do

Automatically create issues

  • When product features change, automatically create an issue for the legal team to revise the terms of service
  • When there’s an outage, automatically notify customer service so they can be ready to address trouble reports
  • If a customer support request requires development work, auto create the issue and assign it to the right team lead

Add watchers

  • Automatically add previous assignees as watchers

Add comments

  • Add a comment to any automatically closed issues, explaining why and how to reopen issues if needed
  • Add a canned response based on a label

Communicate requirements

  • Require users to link issues to their related initiative
  • Automatically remind business owners to attach project requirements

Update Information

Automatically update issues based on certain criteria

  • Assign issues based on custom field data like a certain skill needed or a specific office location
  • Automatically assign issues to users in a list
  • Add high priority bugs to the “Next unreleased version”
  • Set a due date based on a creation date
  • Update issues based on a JQL result
  • Automatically log work on a workflow transition
  • Update information in a child issue with information from the parent
  • Automatically update the due date for all linked issues

Automatically transition issues

  • If a code review is rejected in Crucible, automatically transition the Jira issue back to “To Do” status and notify the developer that there’s a problem
  • If a code branch is created in Bitbucket, automatically transition the Jira issue from the “To Do” status to the “In Progress” status
  • Automatically reopen a closed issue if a customer adds a comment
  • Close an Epic when it’s Stories are closed
  • Close all Sub-tasks when a Task is abandoned

Conditionally update issues

  • Only update issues with a specific priority level
  • Only update issues with a certain component selected

Log additional details

  • When an approval is given, add the user’s name and the timestamp to custom fields, to easily see and report on that information

Automatically increment a number field each time an event occurs

  • Count how many times an issue went into the “On Hold” status, was reopened, or was reassigned

Repeat Frequent Tasks

Create issues on a specific or recurring schedule

  • Automatically create all scheduled maintenance tasks each quarter
  • Automatically create all regression testing tasks
  • Clone an issue each week for the next two years

Create issues based on components

  • For each new hire, automatically create an issue for each application or resource the user needs
  • For each new product, automatically create all the marketing tasks

Create reminders

  • Create sub-tasks to remind yourself to log time at the end of each week
  • Remind the customer to verify their request is resolved
  • Remind the assignee to review an issue not updated in the last two days

Calculate information

  • Automatically calculate the hardware purchase cost based on quantity
  • Automatically calculate the level of effort based on estimates
  • Automatically calculate the mileage fee based on travel miles
  • Automatically calculate the training cost based on number of requests
  • Sub all logged time for an initiative

Create related issues

  • When a request requires development work, automatically create an issue for the dev team and link it to the customer request

Sync Information

Updated related issues

  • When information changes in a parent task automatically update the child task
  • Use regex to find issues mentioned in other fields and automatically link them together

Sync data between multiple Jira applications

  • Sync information once an hour or once a day

Sync data with other tools

  • When case details are added in Salesforce, automatically provide that information in the related Jira issue
  • Automatically create requests from emails or chat conversations

Perform Maintenance

Delete old data

  • Automatically delete old attachments to free up space or for compliance reasons

Schedule admin tasks

  • Periodically look for changes in the list of users with application administrator access

Close old issues

  • Schedule a JQL query to find all bugs older than 2 years and automatically close them
  • Close all requests not updated by the customer in 7 days

Close duplicate issues

  • When an incomplete issue is linked as a dupe, automatically transition the issue to “Done”

Send Alerts

Meet deadlines

  • Find overdue tasks and alert the project manager
  • Notify agents of approaching SLA deadlines
  • Alert the hiring manager one week before a new hire arrives
  • Send an alert when a project reaches 80% of it’s budget

Manage missing information

  • Alert an employee if their expense reimbursement issue is missing receipt attachments
  • Alert a project manager if an important task is missing approval

Surface high priority information

  • Send alerts for high priority bugs, incidents, or impactful issues
  • Detect and alert users to specific problems or key phrases

Catch undesired behavior

  • Detect the word “password” to make sure a user hasn’t exposed their credentials
  • Catch users skipping the QA test step before work is deployed to production

Have more ideas? Share them in the comments section below!

How Automation Makes Us Unstoppable

Where are you on your Jira journey?  Automation means different things to different people and we’re all likely at different stages of our journey.

Level 1

If you’re still using paper forms to request things at your organization, then adopting Jira might be the first step in automating your processes.

Level 2

Then after using Jira for a little while, you start to explore the built-in time saving features like component auto assignment, workflow behaviors like triggers, conditions, validators, and post functions, and custom notification events.

Level 3

And finally, there’s the third level, where you want to extend Jira past its standard capabilities with apps, integrations, or scripting.

Let’s uncover the capabilities in level 3! Tempo is proud to present this recording with Rachel Wright showing real life use cases and how you can benefit from automating your Jira instance. This session includes opportunities, 25 ways automation can make your life easier, and real examples featuring Jira Cloud’s built-in automation and marketplace apps like: Automation for Jira, Jira Miscellaneous Workflow Extensions (JMWE), Jira Workflow Toolbox, and JSU Automation Suite for Jira Workflows.

Watch the recording on Tempo’s website or on YouTube.

Need help?

Need help automating, managing, or migrating your Atlassian products? Get help

Project Administration Links in Jira Software and Jira Service Management

If you have Jira Software and Jira Service Management, how do you know which project admin links are for Jira project settings and which are for service management features?

While both Jira Software and Jira Service Management settings work together to power support projects, it’s helpful to know which links are for which application type so you can consult the correct documentation and information.

Here’s a handy list and and some differences between links in the Cloud and Server deployment types.

Project Admin Area

To get to a project’s admin area click the “Project settings” link in any Service Management project. It’s at the bottom of a project’s left sidebar. In Jira Server, the link takes the admin to the “Request types” page by default. In Cloud, the link takes the admin to the “Details” page by default.

Service project admin in Server

In Server, the first set of sidebar settings are common to all Jira projects. Those links include: Summary, Details, Re-index project, and Delete project.

Further down the page are settings specific to Jira Service Management (JSM) projects. The first link in the section is labeled “Request types”.

The additional links below are for standard Jira project settings like issue types, workflows, screens, and more. You might also have additional links for managing third-party app settings.


Service project admin in Cloud

In Cloud, the Jira and JSM settings are ordered differently.  For example, the second section shows the Jira issue types and the JSM request types together.

Settings List

Here’s a handy list of the typical sidebar links and which application type they belong to.

Jira Software

The following settings are used by software-type projects:

  • Summary
  • Details
  • People (Cloud only)
  • Re-index project (Server only)
  • Delete project
  • Issue types
  • Workflows
  • Screens
  • Fields
  • Priorities
  • Versions
  • Components
  • Users and roles (Server only)
  • Permissions
  • Issue Security
  • Notifications
  • Project links
  • Development tools
  • Issue collectors

Jira Service Management

The following settings are used by service-type projects:

  • Change Management (Cloud only)
  • Request types
  • Customer permissions
  • Language support
  • Portal settings
  • Email requests
  • Customer notifications
  • Widget (Cloud only)
  • Satisfaction settings
  • Knowledge base
  • SLAs
  • Calendars
  • Automation
  • Apps (Cloud only)
  • Incident management (Server only)

Need help using or configuring Jira Software or Jira Service Management settings? Take my LinkedIn Learning courses to understand capabilities and best practices.

Rachel Wright’s Jira Courses on LinkedIn

Default Jira Notifications


Default notification scheme (Jira Software Cloud)

Sometimes it’s important to understand how far your Jira application has strayed from the default configuration. Was that setting there from the beginning or did an application administrator add it eons ago?

To find out, visit Admin > Issues > Notification schemes in your application. Then use this baseline list to compare your Jira settings to the default.

Initial settings for Jira Cloud and Jira Server/Data Center v8.15 are included below. I keep fresh and untouched application instances around so you don’t have to!

Jira Software Cloud, Server & Data Center Notifications

Issue Created (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Updated (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Assigned (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Resolved (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Closed (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Commented (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Comment Edited (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Comment Deleted (System)

Notifications:  none

Issue Reopened (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Deleted (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Moved (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Work Logged On Issue (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Work Started On Issue (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Work Stopped On Issue (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Worklog Updated (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Issue Worklog Deleted (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

Generic Event (System)

Notifications:

  • Current Assignee
  • Reporter
  • All Watchers

See also: Default Jira Global Permissions | Default Jira Project Permissions | Default Jira Notifications

Default Jira Project Permissions

Default permission schemes (Jira Software Cloud)

Sometimes it’s important to understand how far your Jira application has strayed from the default configuration. Was that setting there from the beginning or did an application administrator add it eons ago?

To find out, visit Admin > Issues > Permission schemes in your application. Then use this baseline list to compare your Jira settings to the default.

Initial settings for Jira Cloud and Jira Server/Data Center v8.15 are included below. I keep fresh and untouched application instances around so you don’t have to!

Jira Software Cloud Free & Standard Project Permissions

Scheme name: Default Permission Scheme

Project permissions

Administer Projects

Ability to administer a project in Jira.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Browse Projects

Ability to browse projects and the issues within them.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Manage sprints

Ability to manage sprints.

Granted to:

  • Project role
    • atlassian-addons-project-access

View Development Tools

Allows users in a software project to view development-related information on the issue, such as commits, reviews and build information.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

View Read-Only Workflow

Users with this permission may view a read-only version of a workflow.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Issue permissions

Assignable User

Users with this permission may be assigned to issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Assign Issues

Ability to assign issues to other people.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Close Issues

Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Create Issues

Ability to create issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Delete Issues

Ability to delete issues.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Edit Issues

Ability to edit issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Link Issues

Ability to link issues together and create linked issues. Only useful if issue linking is turned on.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Modify Reporter

Ability to modify the reporter when creating or editing an issue.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Move Issues

Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project they have the create permission for.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Resolve Issues

Ability to resolve and reopen issues. This includes the ability to set a fix version.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Schedule Issues

Ability to view or edit an issue’s due date.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Set Issue Security

Ability to set the level of security on an issue so that only people in that security level can see the issue.

Granted to:

  • Project role
    • atlassian-addons-project-access

Transition Issues

Ability to transition issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Voters & watchers permissions

Manage Watchers

Ability to manage the watchers of an issue.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

View Voters and Watchers

Ability to view the voters and watchers of an issue.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Comments permissions

Add Comments

Ability to comment on issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Delete All Comments

Ability to delete all comments made on issues.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Delete Own Comments

Ability to delete own comments made on issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Edit All Comments

Ability to edit all comments made on issues.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Edit Own Comments

Ability to edit own comments made on issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Attachments permissions

Create Attachments

Users with this permission may create attachments.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Delete All Attachments

Users with this permission may delete all attachments.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Delete Own Attachments

Users with this permission may delete own attachments.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Time tracking permissions

Delete All Worklogs

Ability to delete all worklogs made on issues.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Delete Own Worklogs

Ability to delete own worklogs made on issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Edit All Worklogs

Ability to edit all worklogs made on issues.

Granted to:

  • Project role
    • Administrators
    • atlassian-addons-project-access

Edit Own Worklogs

Ability to edit own worklogs made on issues.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Work On Issues

Ability to log work done against an issue. Only useful if Time Tracking is turned on.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Scheme name: Default software scheme

Same as the Jira Cloud “Default Permission Scheme” except:

Manage sprints

Ability to manage sprints.

Granted to:

  • Project role
    • atlassian-addons-project-access
  • Application access
    • Any logged in user

Jira Software Server Project Permissions

Scheme name: Default software scheme

Project permissions

Administer Projects

Ability to administer a project in Jira. 

Granted to:

  • Project role
    • Administrators
Extended project administration

Also includes a checkbox to grant extended project administration permissions.

Browse Projects

Ability to browse projects and the issues within them.

Granted to:

  • Application access
    • Any logged in user

Edit SPRINTS

Ability to edit sprint name and goal.

Granted to:  none

Manage sprints

Ability to manage sprints.

Granted to:

  • Project role
    • Administrators

Start/Complete Sprints

Ability to start and complete sprints.

Granted to:  none

View Development Tools

Allows users in a software project to view development-related information on the issue, such as commits, reviews and build information.

Granted to:

  • Application access
    • Any logged in user

View Read-Only Workflow

Users with this permission may view a read-only version of a workflow.

Granted to:

  • Application access
    • Any logged in user

Issue permissions

Assignable User

Users with this permission may be assigned to issues.

Granted to:

  • Application access
    • Any logged in user

Assign Issues

Ability to assign issues to other people.

Granted to:

  • Application access
    • Any logged in user

Close Issues

Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.

Granted to:

  • Application access
    • Any logged in user

Create Issues

Ability to create issues.

Granted to:

  • Application access
    • Any logged in user

Delete Issues

Ability to delete issues.

Granted to:

  • Project role
    • Administrators

Edit Issues

Ability to edit issues.

Granted to:

  • Application access
    • Any logged in user

Link Issues

Ability to link issues together and create linked issues. Only useful if issue linking is turned on.

Granted to:

  • Application access
    • Any logged in user

Modify Reporter

Ability to modify the reporter when creating or editing an issue.

Granted to:

  • Project role
    • Administrators

Move Issues

Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project they have the create permission for.

Granted to:

  • Application access
    • Any logged in user

Resolve Issues

Ability to resolve and reopen issues. This includes the ability to set a fix version.

Granted to:

  • Application access
    • Any logged in user

Schedule Issues

Ability to view or edit an issue’s due date.

Granted to:

  • Application access
    • Any logged in user

Set Issue Security

Ability to set the level of security on an issue so that only people in that security level can see the issue.

Granted to:  none

Transition Issues

Ability to transition issues.

Granted to:

  • Application access
    • Any logged in user

Voters & watchers permissions

Manage Watchers

Ability to manage the watchers of an issue.

Granted to:

  • Project role
    • Administrators

View Voters and Watchers

Ability to view the voters and watchers of an issue.

Granted to:

  • Application access
    • Any logged in user

Comments permissions

Add Comments

Ability to comment on issues.

Granted to:

  • Application access
    • Any logged in user

Delete All Comments

Ability to delete all comments made on issues.

Granted to:

  • Project role
    • Administrators

Delete Own Comments

Ability to delete own comments made on issues.

Granted to:

  • Application access
    • Any logged in user

Edit All Comments

Ability to edit all comments made on issues.

Granted to:

  • Project role
    • Administrators

Edit Own Comments

Ability to edit own comments made on issues.

Granted to:

  • Application access
    • Any logged in user

Attachments permissions

Create Attachments

Users with this permission may create attachments.

Granted to:

  • Application access
    • Any logged in user

Delete All Attachments

Users with this permission may delete all attachments.

Granted to:

  • Project role
    • Administrators

Delete Own Attachments

Users with this permission may delete own attachments.

Granted to:

  • Application access
    • Any logged in user

Time tracking permissions

Delete All Worklogs

Ability to delete all worklogs made on issues.

Granted to:

  • Project role
    • Administrators

Delete Own Worklogs

Ability to delete own worklogs made on issues.

Granted to:

  • Application access
    • Any logged in user

Edit All Worklogs

Ability to edit all worklogs made on issues.

Granted to:

  • Project role
    • Administrators

Edit Own Worklogs

Ability to edit own worklogs made on issues.

Granted to:

  • Application access
    • Any logged in user

Work On Issues

Ability to log work done against an issue. Only useful if Time Tracking is turned on.

Granted to:

  • Application access
    • Any logged in user

Scheme name: Default software scheme

Same as the Jira Server “Default Permission Scheme”.

Jira Software Data Center, Jira Cloud Premium, and Jira Cloud Enterprise Project Permissions

These types of Jira have archival features and additional permissions. Same as the Jira Server “Default Permission Scheme” plus:

Browse Project Archive

Ability to browse archived issues from a specific project.

Granted to:  none

Archive Issues

Ability to archive issues for a specific project.

Granted to:  none

Restore Issues

Ability to restore issues for a specific project.

Granted to:  none

See also: Default Jira Global Permissions | Default Jira Project Permissions | Default Jira Notifications

Default Jira Global Permissions

Global Permissions (Jira Cloud)
Global Permissions (Jira Cloud)

Sometimes it’s important to understand how far your Jira application has strayed from the default configuration. Was that setting there from the beginning or did an application administrator add it eons ago?

To find out, visit Admin > System > Global permissions in your application. Then use this baseline list to compare your Jira settings to the default.

Initial settings for Jira Cloud and Jira Server/Data Center v8.15 are included below. I keep fresh and untouched application instances around so you don’t have to!

Jira Software Cloud Global Permissions

Administer Jira

Create and administer projects, issue types, fields, workflows, and schemes for all projects. Users with this permission can perform most administration tasks, except: managing users, importing data, and editing system email settings.

Users/Groups:

  • system-administrators
  • atlassian-addons-admin
  • site-admins
  • trusted-users-xxx (unique alphanumeric string)
  • administrators
  • jira-administrators

Browse users and groups

View and select users or groups from the user picker, and share issues. Users with this permission can see the names of all users and groups on your site.

Users/Groups:

  • system-administrators
  • site-admins
  • jira-software-users
  • administrators
  • jira-administrators
  • atlassian-addons-admin

Share dashboards and filters

Share dashboards and filters with other users.

Users/Groups:

  • atlassian-addons-admin
  • jira-software-users
  • system-administrators
  • jira-administrators
  • site-admins
  • administrators

Manage group filter subscriptions

Create and delete group filter subscriptions.

Users/Groups:

  • jira-administrators
  • jira-software-users
  • administrators
  • system-administrators
  • atlassian-addons-admin
  • site-admins

Make bulk changes

Modify collections of issues at once. For example, resolve multiple issues in one step.

Users/Groups:

  • atlassian-addons-admin
  • jira-software-users
  • site-admins
  • administrators
  • jira-administrators
  • system-administrators

Create next-gen projects

Create projects separate from shared configurations and schemes. Next-gen projects don’t affect existing projects or shared configurations like workflows, fields or permissions. Only licensed users can create next-gen projects.

Users/Groups:

  • Public, anyone on the internet, including logged in and anonymous users.

Jira Software Server & Data Center Global Permissions

Jira System Administrators

Ability to perform all administration functions. There must be at least one group with this permission.

Users/Groups:

  • jira-administrators

Jira Administrators

Ability to perform most administration functions (excluding Import & Export, SMTP Configuration, etc.).

Users/Groups:

  • jira-administrators

Browse Users

Ability to select a user or group from a popup window as well as the ability to use the ‘share’ issues feature. Users with this permission will also be able to see names of all users and groups in the system.

Users/Groups:

  • jira-administrators
  • jira-servicedesk-users (If installed)
  • jira-software-users

Create Shared Objects

Ability to share dashboards and filters with other users, groups and roles.

Users/Groups:

  • jira-administrators
  • jira-servicedesk-users (If installed)
  • jira-software-users

Manage Group Filter Subscriptions

Ability to manage (create and delete) group filter subscriptions.

Users/Groups:

  • jira-administrators
  • jira-servicedesk-users (If installed)
  • jira-software-users

Bulk Change

Ability to modify a collection of issues at once. For example, resolve multiple issues in one step.

Users/Groups:

  • jira-administrators
  • jira-servicedesk-users (If installed)
  • jira-software-users

Browse Archive

Ability to browse all archived issues.

Users/Groups:

  • None (empty)

See also: Default Jira Global Permissions | Default Jira Project Permissions | Default Jira Notifications

Books

Jira Strategy Admin WorkbookJira Strategy Admin Workbook TranslationsThe Ultimate Guide to Jira MigrationsEffective Jira AdministrationBattling Jira Custom Field BloatBetter Form Design in Jira

Jira Strategy Admin Workbook

JIRA Strategy Admin Workbook

The Jira Strategy Admin Workbook will save you time, money and frustration. This book is different – it’s not documentation.  It’s recommendations from years of cleaning up horrible Jira configurations! It’s about what you should do, what you shouldn’t do, and why.

Read more or buy now

Jira Strategy Admin Workbook Translations

Get the admin workbook in additional languages.

See translations

The Ultimate Guide to Jira Migrations: How to migrate from Jira Server to Data Center or Cloud

Rachel Wright teamed up with Atlassian Solution Partner Botron Atlassian Apps to create this 180 page master resource to answer all your migration questions and provide a comprehensive plan to follow.

Download from Botron

Effective Jira Administration

This 64 page book from ThinkTilt and Rachel Wright helps you bring the benefits of Jira to more teams in your organization.   The book includes tips for governance, administration, maintenance, best practices, and more.

Buy now

Battling Jira Custom Field Bloat

How many custom fields do you have? For most of us the answer is, “Too many!” ThinkTilt and Rachel Wright collaborated again to produce this 35 page book to help you audit, delete, reduce, and manage your Jira custom fields.

Buy now

Better Form Design in Jira

The latest ThinkTilt and Rachel Wright collaboration. This 57 page book helps you convert paper forms to Jira, choose the right field types, and create efficient forms and screens in Jira and Jira Service Management.

Buy now

繁體中文翻譯

這些翻譯的奇妙翻譯,編輯和審閱者是:

鐘冠智 Kerwin
現任Atlassian 大中華區負責人
前CSDN Atlassian Agile DevOps諮詢顧問
大中華區首位ACP-100認證專家
Atlassian 中文社群發起人

數位轉型的時代——「每家公司都是IT公司」大勢所趨,敏捷DevOps成為轉動這一齒輪最重要的推手。尤其,Atlassian被喻為「敏捷DevOps界的愛馬仕」,其明星產品Jira在這波浪潮中紅遍大江南北。台積電、聯發科、鴻海、滴滴出行、華為、中石油、百度、中國移動,乃至美國航天局NASA、Spotfy——全球500強企業中,超過80%公司成功使用Jira實現他們的敏捷DevOps轉型。

2018年年初,中國Jira社區一成立,年底立馬突破1000人,無論是敏捷教練,DevOps專家,還有各家Jira管理員和用戶們,紛紛投入探討落地實施研究,Jira之火在中國市場不斷延燒。而Jira之所以能穩坐敏捷DevOps工具鏈寶座,絕對歸功於強大的開放兼容性,它可以和各家開源與商用軟件接口,包括Gitlab,Jenkins,Azure DevOps,Sonarqube等,形成龐大的生態圈。

另我驚訝的是,儘管Jira在Agile DevOps扮演舉足輕重的地位,至今中國市場上仍然沒有任何一本關於Jira的中文專書。

回想起北京2018年第一次的社群大會,當時社區發起人之一的馬亮和我說,「有這麼多優秀的Jira老師和用戶,為何沒有一本正式的書籍?鐘老師要不咱們來翻譯看看。」 我馬上想到之前在準備ACP-100證照讀到的優質好書《Jira Admin Stragtegy Workbook》。

本書作者Rachel Wright是全球第一批考取ACP-100認證的Jira專家,擁有多年實務經驗,協助許多公司將Jira落地實施。在眾多的外文Jira相關書籍中,我特別挑選本書作為中文版第一本Jira專書,系因作者寫作思路清晰,把許多坑毫無隱藏地揭露給所有讀者。作為多年的Jira專家的我,看了這樣無私的分享,真心覺得相見恨晚——「那些年我們跳過的坑」:field地獄,複雜資料庫,失控的workflow等等,在該書中都提出了良好的建議。很多事情如果能夠提前一步知道該有多好,預防勝於治療,非常推薦大家一定要閱讀本書。

我特別將本書推薦給三種讀者,第一,資深Jira管理員,它山之石可以攻玉,通過看到別的人的經驗來學習,避免自己許多跳坑的過程。第二,希望考取ACP-100的團隊,這個考試非常重視對於Jira的熟悉度和管理經驗,只看手冊的人很難具備這些知識,本書豐富的經驗分享,非常適合備考的朋友們。第三,新入行的Jira管理員或是有興趣研究的用戶,本書深入淺出的介紹,會讓各位很快地瞭解這樣強大的工具如何實際落地。

非常感謝作者Rachel的信任,也感謝來自Jira社群的共同譯者-黃俊耀參與本次Sample書繁體版的投入。謝謝各位小夥伴們的投入,才造就這本翻譯書問世,期待之後繼續一起投入貢獻Jira社群。最後,非常感謝我的太太之穎照顧剛出生的兒子天夏,一路陪伴著我,讓我充滿動力持續向前;更感謝我所認識的上帝,將一切榮耀頌贊都歸給祢。


黃俊耀 Daniel
現任職某外商遊戲公司資深QA
ACE leader, Taipei
Microsoft MVP Reconnect

使用 Atlassian 產品已經有四年多的時間,Jira的開放性與多樣變化讓我們能夠運用合理的資源,快速地將不同團隊使用的工具,從需求到開發測試,以及後續問題追蹤並進行整合分析。正是這樣的魅力,讓我對Jira愛不釋手。

隨著團隊的需求成長,在學習的過程中讓我驚訝的是,相較於國外的參考資訊,中文的工具書顯得十分稀有。2019年的五月我參加了在上海舉辦的Atlassian企業日,在因緣際會下認識了Atlassian中文社群的發起人Kerwin,在與當日講師及其他業界同好交流DevOps和Jira使用經驗後,對於因中文化而蓬勃發展的用戶社群及豐富的參考案例感到無比興奮,更燃起了想將更多繁體中文內容推廣給本地Jira使用者及社群的念頭。

這次感謝Kerwin的牽線而能有機會翻譯《Jira Strategy Admin Workbook》樣書,也希望能夠讓更多繁體中文使用者深入認識Jira。這本書不僅能幫助資深管理者在面對系統時,能提早發現潛在的問題,從而將危機消弭於無形;深入淺出的說明也適合新手Jira管理員作為入門參考手冊,透過作者Rachel Wright的親身經驗迅速提升自身功力。

Jira不一定是最敏捷的管理工具,但這本書絕對能幫助你迅速上手展開全面性的部署。


Translations
We're exploring offering the Jira Strategy Admin Workbook in additional languages. Tell us which language(s) you're interested in! Enter your email address (optional) and we'll notify you when a translation is ready.
Which language(s) should the Jira Strategy Admin Workbook be offered in?