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?

繁體中文

Traditional Chinese

Jira策略管理實戰手冊: 為系統管理員提供設定、清理和維護Jira的範本

作者:  Rachel Wright
譯者:Kerwin Chung & Daniel Huang

此實戰手冊包含:

  • 152條建議- 幫助您設置、清理和維護Jira,
  • 50個工作表,以及其他相關範本、片段程式码和范例- 幫助您建立和簡化主要workflow,
  • 33個需避免的反面真實案例,
  • 每個管理區域的最佳實踐和注意事項,
  • 我作為管理員犯下的十大錯誤,以及 •其他地方無法提供的內容。

此實戰手冊向您展現:

  • 精心策劃並得以實施的執行項目,
  • workflow管理的簡單方法,
  • 如何審計及清理系統,
  • 維護和擴展Jira的方法,
  • 如何新建可重複的流程,以及 •如何遠離“Jira沼澤”。

譯者

關於翻譯,編輯和審稿人

示例章節

下載樣本

简体中文

Simplified Chinese

Jira策略管理实战手册: 为应用程序管理员提供配置、清理和维护Jira的模板

作者:雷切尔赖特
译者:Kerwin Chung

此实战手册包含:

  • 152条建议- 帮助您设置、清理和维护Jira,
  • 50个工作表,以及其他相关模板、代码片段和示例- 帮助您建立和简化主要工作
  • 33个需避免的反面真实案例,
  • 每个管理区域的最佳实践和注意事项,
  • 我作为管理员犯下的十大错误,以及
  • 其他地方无法提供的内容。

此实战手册向您展现:

  • 精心策划并得以实施的行动项,
  • 工作流管理的简单方法,
  • 如何审计及清理应用程序,
  • 维护和扩展Jira的方法,
  • 如何创建可重复的流程,以及
  • 如何远离“Jira沼泽”。

前言

数字化转型的时代——“每家公司都是IT公司”大势所趋,敏捷DevOps成为转动这一齿轮最重要的推手。尤其,Atlassian被喻为”敏捷DevOps界的爱马仕”,其明星产品Jira在这波浪潮中红遍大江南北。滴滴出行、华为、中石油、百度、中国移动,乃至美国航天局NASA、谷歌——全球500强企业中,超过200家公司成功使用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专家的我,看了这样无私的分享,真心觉得相见恨晚——“那些年我们跳过的坑”:字段地狱,复杂数据库,失控的工作流等等,在该书中都提出了良好的建议。很多事情如果能够提前一步知道该有多好,预防胜于治疗,非常推荐大家一定要阅读本书。

我特别将本书推荐给三种读者,第一,资深Jira管理员,它山之石可以攻玉,通過看到別的人的经验来学习,避免自己许多跳坑的过程。第二,希望考取ACP-100的团队,这个考试非常重视对于Jira的熟悉度和管理经验,只看手册的人很难具备这些知识,本书丰富的经验分享,非常适合备考的朋友们。第三,新入行的Jira管理员或是有兴趣研究的用户,本书深入浅出的介绍,会让各位很快地了解这样强大的工具如何实际落地。

非常感谢作者Rachel的信任,也感谢来自Jira社区的共同译者:关群,周琦,马亮,闫锦维,刘旭东,马畅。谢谢各位小伙伴们的投入,才造就这本翻译书问世,期待之后继续一起投入贡献Jira社区。最后,非常感谢我的太太之颖照顾刚出生的儿子天夏,一路陪伴著我,让我充满动力持续向前;更感谢我所认识的上帝,将一切荣耀颂赞都归给祢。

钟冠智 Kerwin
现任Atlassian 大中华区负责人
前CSDN Atlassian Agile DevOps谘询顾问
大中华区首位ACP-100认证专家
Atlassian 中文社区发起人

中文翻译

关于翻译,编辑和审稿人

Included Materials (English)

Download the worksheets, templates, and companion materials using the coupon code in your book’s “Worksheets, Templates & Companion Materials” section.  The following are downloadable after your book purchase:

  1. Atlassian Summit Notes
  2. Determine Jira Permissions
  3. Jira Add User Instruction Based on Issue ID
  4. Jira Annual Report
  5. Jira Application Administrator Responsibilities
  6. Jira Application Comparison
  7. Jira Automated Testing
  8. Jira Bulk Import
  9. Jira Change Select List Formatting
  10. Jira Clean Instance
  11. Jira Conditional Announcement Banner
  12. Jira Custom Workflow Documentation
  13. Jira Database Queries
  14. Jira Detailed Upgrade Plan
  15. Jira Genie and Jira Gerbil Character Users
  16. Jira HTML Links
  17. Jira Incident Log
  18. Jira Issue Creation via Email Instructions
  19. Jira Issue Security Worksheets
  20. Jira Menu and Transition Buttons Graphic
  21. Jira Monitoring
  22. Jira New Custom Field Requests
  23. Jira New Project Configuration Checklist
  24. Jira New Project Request
  25. Jira New User Communication and Checklist
  26. Jira New User Request
  27. Jira Notification Scheme
  28. Jira Permission Scheme Worksheets
  29. Jira Plugin and Add-on Vetting Procedure
  30. Jira Plugin Tracking
  31. Jira Project Status
  32. Jira Project Wording
  33. Jira Recommendations and Tips
  34. Jira REST API and Database Users
  35. Jira Rollback Plan
  36. Jira Scheduled Maintenance
  37. Jira Scheme Wording
  38. Jira Security Policy Considerations
  39. Jira Standard Capabilities
  40. Jira Standard Regression Testing
  41. Jira Status Update Email Notification Instructions
  42. Jira Support and Emergency Escalation
  43. Jira System Stats
  44. Jira Upgrade Wording
  45. Jira Use and Future Predictions
  46. Jira Users Wording
  47. Jira Workflow XML
  48. New Jira Features
  49. Sample Jira Support Project Set Up
  50. Top Jira Support Measurements

Download the files individually or a few at a time as you need them. You can also download them all at once, in one .zip file. See download instructions.

Jira策略管理实战手册

从亚马逊获取
获取印刷版

Translations

简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)

Translation Request

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?

Jira User Best Practices

As organizations continue to adopt digital technology, more and more teams are leveraging Jira to track their work. Here are some do’s and don’ts for Jira users.

Do

Here are some best practices and good habits:

Create Jira issues

Create a Jira issue any time you need to track a task. Jira can handle many millions of issues, so don’t worry about filing too many. Also, you can’t really break anything in Jira, so don’t be afraid to use it! The only thing your administrator can’t undo is deletion of data.

Break up large tasks into smaller ones

If you’re working on something big, create multiple issues to break it up into small, manageable chunks. For example, if the task is to make a cake, break that up into different sub-tasks for ingredient shopping, for mixing and baking the ingredients, and for icing the cake after it’s cooled. Ask your Jira Administrator about issue hierarchy in your application.

Breaking up work is also the way to assign multiple people to similar tasks.

Transition issues as you work

Transition issues forward in the workflow as you work on them in real-time. It’s your responsibility to make sure an issue’s current status mirrors reality.

Keep issue details accurate

Keep all issue details and fields up to date. It’s important to complete as many fields as possible and update them as soon as information changes. It’s OK if additional details become available after an issue is created. Add it to Jira right away so everyone has the best information.

Accurate information helps others find issues and generate reports. When an issue is complete, its information should serve as a legal and historical record of what was done.

Take action on issues assigned to you

If an issue is assigned to you, it means you need to take action! Look at the status to see what to do and look in the comments field for any notes left for you.

Fix incorrect assignments

If an issue is assigned to the wrong person simply change the assignee. Unassigned or incorrectly assigned issues create unnecessary delays.

Record action details

When you’ve completed an issue, add a comment explaining what you did, where or how you did it, and anything else others should know right now or in the future.

In the example, a typo on the company website was reported.

I fixed the typo and then added a comment showing I corrected the spelling of the word “customer”, that the change occurred in the first paragraph on the page, and the page I changed was named “terms.html”. 

Now anyone who needs to verify my change knows exactly what to look for and where.  This is just good record keeping.

Log time

When you’ve completed an issue, log how much time it took to complete.  Get into this good habit, even if your organization doesn’t require it.

Logging work is NOT about how good or fast you are!  It’s about planning, prioritization, allocation of resources, and improving estimation for future similar tasks.

For example, if my estimate is 1 hour and I’ve logged 3 hours so far, this could signal there are other factors making this task take longer than expected. Maybe the code is super complex, maybe I could some help clearing road blocks, or maybe I simply mis-estimated.  In the real world, these things happen all the time!  Jira just gives you a way to show it.

A final thought on time logging:

Do you submit a time card or a report of what you’re working on?  Jira can handle both those things for you.  No need for extra manual work!  Ask your Jira Administrator about progress reporting and time logging in your Jira application.

Don’t

Now let’s cover a few things not to do:

Delete issues

If you don’t need an issue, it’s smarter to simply close it rather than delete it.  Use the “Resolution” field to indicate no work is needed because it’s invalid, can’t be reproduced, is a duplicate, or won’t be fixed.

Report an issue and walk away

If you create an issue, you should follow it through to completion, be ready to verify the resolution, and be available to answer questions.  If you create an issue and walk away, it might not be addressed any time soon.

Enter sensitive information

Don’t enter sensitive information into Jira or other applications.  This is sometimes referred to as PII (personally identifiable information) or SPI (sensitive personal information).

Sensitive information includes passwords, personal data (social security numbers and mother’s maiden names), health information (like which health insurance plan an employee has) employment information (like citizen status or salary), and any proprietary or confidential personal or company information.

Contact your Jira Administrator, Security, Legal, and Compliance teams for any company-specific policies.

Also read: 9 Tips for Getting Action in Jira