Below is a brief summary of each of the Content Auditor sections (viewed as links in the application.
This section contains charts that are a visual representation of the Content Auditor sections (Global, Project, Scheme, JSM and Instance. The bar charts were created to give the user a quick overview of the totals contained on each tab under this area. |
This section contains charts that provide a breakdown of key metric areas that are essential to the daily duties of a Jira Administrator. Metrics such as a breakdowns of:
|
This section represents content in Jira that is at a global level or another way of stating this is it is not project specific. The following information can be found under this area in tabular format:
|
This section represents content in Jira that is at the project level or content that is closer to the daily operations of Jira projects:
|
This section provides a summary of content that is specific to the schemes. Information on the following schemes can be obtained:
|
This section is specific to Jira Service Management projects. While JSM projects are also listed under the projects area of the Global Content Auditor section, they have been split out as it appears that Atlassian will evolve the JSM REST API with functionality that is specific to these types of projects. The following areas are represented in this section:
|
This section provides a summary of content at the system level of Jira. While it is expected that Jira Administrators would not use this section as much as the others, it was created to provide the administrators with a quick and easy way to get key information about their Jira instance. Most notably, the main Global Settings can be found here without needless scrolling through a full list of other, undesired system settings. The following tabs can be found under this section:
NOTE: There will be times when the User Email column will not display an actual email address. This is by design at the Atlassian level where users have the option to display or hide their email address. If the user has hidden their email via the profile setting, you’ll see “User has blocked email visibility” in the column instead. In the event, it is an account that is linked to the installation of an Atlassian App, you see “App account” in the column. NOTE: There will be times when the User Email column will not display an actual email address. This is by design at the Atlassian level where users have the option to display or hide their email address. If the user has hidden their email via the profile setting, you’ll see “User has blocked email visibility” in the column instead. In the event, it is an account that is linked to the installation of an Atlassian App, you see “App account” in the column.
|