- JIRA 5.2 Essentials
- Table of Contents
- JIRA 5.2 Essentials
- Credits
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Getting Started with JIRA
- 2. Project Management
- 3. Issue Management
- 4. Field Management
- 5. Screen Management
- 6. Workflows and Business Processes
- Mapping business processes
- Understanding workflows
- Managing workflows
- Creating a workflow
- Editing a workflow
- Publishing a draft
- Steps and issue statuses
- Transitions
- Configuring a transition
- Using the workflow designer
- Deleting a workflow
- Copying a workflow
- Importing/exporting a workflow
- Using the JIRA workflow sharing plugin
- Using other workflow plugins
- Workflow schemes
- The Help Desk project
- Summary
- 7. E-mails and Notifications
- JIRA and e-mail
- Mail servers
- Working with outgoing mails
- Mail queues
- Manually sending e-mails
- Events
- Notifications
- The notification scheme
- Troubleshooting notifications
- Incoming e-mails
- Adding an incoming mail server
- Mail handlers
- Creating a new issue or adding a comment to an existing issue
- Adding a comment with the entire e-mail body
- Adding a comment from the non-quoted e-mail body
- Creating a new issue from each e-mail message
- Adding a comment before a specified marker or separator in the e-mail body
- Adding a mail handler
- Editing and deleting a mail handler
- The Help Desk project
- Summary
- 8. Securing JIRA
- 9. Searching, Reporting, and Analysis
- 10. General Administration
- 11. Advanced Features
- Index
Just like notifications, it can be very frustrating to troubleshoot permission settings. To help with this, JIRA also provides a Permission Helper to assist administrators to pinpoint settings that prevent users from accessing certain features.
The Permission Helper works similarly to the Notification Helper:
- Browse to the JIRA administration console.
- Select Permission Helper from under the Admin Helper section.
- Specify the user that is having access problems in the User field.
- Specify the issue to test with.
- Select the permission the user does not have (for example, Edit issue).
- Click on Submit.
As shown in the preceding screenshot, the user Patrick Li cannot edit issues for the DEMO project, because he is not a member of the Developer project role, which is required as per the Default Permission Scheme used.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.