Site Health
It will show overall health of site. i.e you can check reports based on different health parameters
Jira configurations - Reports based on Jira configuration assessments
Users - Reports based on user assessment
Health parameters for Jira configurations
Sr. no | Object type | Health parameter | Description |
|---|---|---|---|
Atlassian Plugin | User installed third party plugins (Connect) | This report provides a detailed list of all Jira plugins (Connect) installed by users. It helps administrators monitor and manage the plugins, ensuring that only necessary and approved plugins are in use, thereby maintaining the system's performance and security. | |
Custom field | Duplicate custom fields | This report provides a comprehensive list of duplicate custom fields within your Jira instance. It identifies custom fields that share the same name or configuration, helping you to streamline your field management and avoid redundancy. The report includes details such as field names, types, and screens count, enabling efficient field consolidation and improved system performance. | |
Custom field | Custom fields not used in any screens | This report identifies custom fields within your Jira instance that are not associated with any screens. It provides a detailed list of these unused custom fields, including their names, types. This information helps you to clean up and optimize your Jira configuration by removing or repurposing unnecessary custom fields, thereby enhancing system performance and maintainability. | |
Custom field | Custom fields with no context | This report lists custom fields in your Jira instance that do not have any associated contexts. It includes details such as field names, types. By identifying these fields, the report helps you to manage and optimize your custom field configurations, ensuring that all fields are effectively utilized and relevant to your projects. | |
Custom field | Custom fields with single global context | This report identifies custom fields in your Jira instance that have only one global context and no other specific contexts. It includes details such as field names, types. By highlighting these fields, the report helps you pinpoint opportunities to add more granular contexts, which can lead to improved performance and more efficient field management tailored to specific projects or issue types. | |
Custom field | 'Select' type field context with no options | This report lists custom fields in your Jira instance that are designed to have options (such as select lists, check-boxes, or radio buttons) but currently have no options configured. It includes details such as field names, types. By identifying these fields, the report helps you clean up and optimize your Jira configuration by removing or repurposing fields that are not in use, thereby enhancing system efficiency and clarity. | |
Field configuration | Orphan field configurations | This report identifies field configurations in your Jira instance that are not associated with any field configuration schemes, making them orphaned. By highlighting these unused configurations, the report assists in cleaning up and optimizing your Jira setup, ensuring that only necessary and active Field configurations are retained, thereby enhancing system organization and efficiency. | |
Field configuration schemes | Orphan field configuration schemes | This report identifies field configuration schemes in your Jira instance that are not associated with any projects, making them orphaned. By highlighting these unused schemes, the report aids in cleaning up and optimizing your Jira setup, ensuring that only relevant and active schemes are maintained, thereby improving system organization and performance. | |
Filter | Filters Associated with Deactivated, Suspended, or Deleted Users in Jira | This report identifies filters in your Jira instance that are associated with deactivated, suspended, or deleted users. It includes details such as filter names, owners. By highlighting these filters, the report assists in maintaining an up-to-date and efficient Jira setup, ensuring that only active and relevant filters are retained, thereby improving system organization and usability. | |
Issue security scheme | Orphan issue security schemes | This report provides a list of issue security schemes that are not associated with any projects in Jira. It helps in identifying and managing these orphaned schemes, allowing for better organization and cleanup of the Jira configuration. | |
Issue type | Issue types only associated to default issue type scheme | This report provides a comprehensive list of issue types that are exclusively associated with the default issue type scheme in Jira. It helps in identifying and managing issue types that are not linked to any custom issue type schemes, ensuring streamlined project configurations and consistency across the board. | |
Issue type scheme | Orphan issue type schemes | This report provides a list of orphan issue type schemes, which are issue type schemes not associated with any projects in Jira. It assists in identifying and managing these unused schemes, allowing for better organization and cleanup of the Jira configuration. | |
Issue type screen scheme | Orphan issue type schemes | This report provides a list of orphan issue type screen schemes, which are not associated with any projects or workflows in Jira. It assists in identifying and managing these unused issue type screen schemes, allowing for better organization and cleanup of the Jira configuration. | |
Notification scheme | Orphan notification schemes | This report provides a list of notification schemes that are not associated with any projects in Jira. It assists in identifying and managing these orphaned schemes, allowing for better organization and cleanup of the Jira configuration. | |
Permission scheme | Orphan permission schemes | This report provides a list of permission schemes that are not associated with any projects in Jira. It assists in identifying and managing these orphaned schemes, allowing for better organization and cleanup of the Jira configuration. | |
Project | Projects with deactivated user as lead | This report provides a list of projects in Jira where the project lead is a deactivated user. It helps in identifying and addressing projects that may require reassignment of the project lead to ensure proper project management and oversight. | |
Project | Project with less than 100 issues | This report provides a list of projects in Jira that have fewer than 100 issues. It helps in identifying smaller projects, which may require special attention or different management strategies compared to larger projects. | |
Project | Projects inactive since last 6 months | This report provides a list of projects in Jira that have been inactive for the past 6 months. It helps in identifying projects that may need to be archived, reviewed, or reactivated to ensure efficient use of resources and project management. | |
Project | Projects with no issues | This report provides a list of projects in Jira that currently have no issues. It helps in identifying projects that may require further investigation to determine their status and whether they should be archived, repurposed, or deleted. | |
Project | More than 5 team managed projects | This report provides a list of users or teams in Jira that are managing more than 5 team-managed projects. It helps in identifying potential over-allocation of resources and ensures that project management responsibilities are balanced and effectively distributed. | |
Project | Projects with more than 50k issues | This report provides a list of projects in Jira that have more than 50,000 issues. It helps in identifying high-volume projects that may require additional resources, performance optimization, or special attention to manage the large number of issues effectively. | |
Screen | Orphan screens | This report provides a list of orphan screens, which are screens not associated with any screen schemes or workflows in Jira. It assists in identifying and managing these unused screens, allowing for better organization and cleanup of the Jira configuration. | |
Screen scheme | Orphan screen schemes | This report provides a list of orphan screen schemes, which are screen schemes not associated with any projects or workflows in Jira. It assists in identifying and managing these unused screen schemes, allowing for better organization and cleanup of the Jira configuration. | |
Status | Statuses unused across all workflow | This report provides a list of statuses that are not used in any workflows in Jira. It assists in identifying and managing these unused statuses, allowing for better organization and cleanup of the Jira configuration. | |
Workflow | Inactive workflows | This report provides a list of inactive workflows in Jira, which are not currently associated with any active projects. It assists in identifying and managing these unused workflows, allowing for better organization and cleanup of the Jira configuration. | |
Workflow | All Workflows with their transition count | This report provides a list of workflows along with the count of transitions within each workflow in Jira. It helps in analyzing the complexity and structure of workflows, enabling administrators to optimize and manage workflow configurations more effectively. | |
Workflow | Workflows using third-party plugins in their transitions | This report provides a comprehensive analysis of workflows that incorporate third-party plugins within their transition processes. It identifies and details the specific workflows that utilize external plugins. | |
Workflow | Workflows eligible for deletion | This report identifies and lists all Workflows that can be deleted from the system. It includes workflows that are not included in any Project(s) and not included in any Workflow Scheme(s), excluding "read-only" workflows. This report is crucial for maintaining a clean and efficient workflow environment by identifying obsolete or unused workflows that can be safely removed. | |
Workflow | Workflows containing draft | This report provides a comprehensive list of all Workflows containing drafts within the system. This report is essential for tracking the progress and status of Workflows that contains draft, ensuring that they are reviewed, finalized, and published in a timely manner. | |
Workflow scheme | Orphan workflow schemes | This report provides a list of orphan workflow schemes, which are not associated with any projects in Jira. It assists in identifying and managing these unused workflow schemes, allowing for better organization and cleanup of the Jira configuration. | |
Custom field | Custom fields unused across all issues | This report lists custom fields in your Jira instance that have no values in any issues, indicating they are not being utilized. It includes details such as field names, types. The report also provides a JQL query for each field, allowing users to confirm the absence of values. This facilitates a reliable cleanup process, helping to optimize your Jira configuration by removing unnecessary fields and improving overall system performance. | |
Field configuration | Identical field configurations | This report identifies field configurations in your Jira instance that are identical to other field configurations.By pinpointing these duplicate or similar configurations, the report helps you streamline and optimize your Jira setup, ensuring that only unique and necessary configurations are retained, thereby enhancing system organization and efficiency. | |
Field configuration scheme | Identical field configuration schemes | This report identifies field configuration schemes in your Jira instance that are identical to other field configuration schemes. By pinpointing these duplicate schemes, the report helps you streamline and optimize your Jira setup, ensuring that only unique and necessary schemes are retained, thereby enhancing system organization and efficiency. | |
Filter | Identical filters | This report identifies filters in your Jira instance that are identical to other filters. It includes details such as filter names, owners. By pinpointing these duplicate filters, the report helps you streamline and optimize your Jira setup, ensuring that only unique and necessary filters are retained, thereby enhancing system organization and efficiency. | |
Issue security schemes | Identical issue security schemes | This report identifies and lists issue security schemes that have identical configurations in Jira. It helps in recognizing duplicate schemes, enabling administrators to consolidate and streamline security configurations for better management and efficiency. | |
Issue type | Issue types unused across all issues | This report identifies and lists all issue types that have not been utilized in any issues across all projects in Jira. It helps in cleaning up and optimizing the issue type schemes by highlighting unused issue types, ensuring that only relevant and actively used issue types are maintained. | |
Issue type scheme | Identical issue type schemes | This report identifies and lists issue type schemes that have identical configurations in Jira. It helps in recognizing duplicate schemes, enabling administrators to consolidate and streamline issue type schemes for better management and efficiency. | |
Issue type screen scheme | Identical issue type screen schemes | This report identifies and lists issue type screen schemes that have identical configurations in Jira. It helps in recognizing duplicate issue type screen schemes, enabling administrators to consolidate and streamline configurations for better management and efficiency. | |
Notification scheme | Identical notification schemes | This report identifies and lists notification schemes that have identical configurations in Jira. It helps in recognizing duplicate schemes, enabling administrators to consolidate and streamline notification configurations for better management and efficiency. | |
Permission scheme | Identical permission schemes | This report identifies and lists permission schemes that have identical configurations in Jira. It helps in recognizing duplicate schemes, enabling administrators to consolidate and streamline permission configurations for better management and efficiency. | |
Project | Identify the project that have same configurations | This report identifies and lists projects in Jira that have identical configurations, including workflows, permission schemes, and notification schemes. It helps in recognizing duplicate configurations, enabling administrators to consolidate and streamline project settings for better management and efficiency. | |
Project | Projects with no role actors | This report provides a list of projects in Jira that currently have no role actors assigned. It helps in identifying projects that may lack proper role assignments, ensuring that necessary roles are filled for effective project management and collaboration. | |
Project | Project is deleted, delete all the unused configurations | This report provides a list of projects that have been deleted in Jira and identifies any unused configurations associated with them, such as workflows, permission schemes, and notification schemes. It helps in cleaning up and removing these unused configurations to maintain a streamlined and efficient Jira environment. | |
Screen | Identical screens | This report identifies and lists screens that have identical configurations in Jira. It helps in recognizing duplicate screens, enabling administrators to consolidate and streamline screen configurations for better management and efficiency. | |
Screen scheme | Identical screen schemes | This report identifies and lists screen schemes that have identical configurations in Jira. It helps in recognizing duplicate screen schemes, enabling administrators to consolidate and streamline screen scheme configurations for better management and efficiency. | |
Status | Identical statuses | This report identifies and lists statuses that have identical names and properties in Jira. It helps in recognizing duplicate statuses, enabling administrators to consolidate and streamline status configurations for better management and efficiency. | |
Workflow | Identical workflows | This report identifies and lists workflows that have identical configurations in Jira. It helps in recognizing duplicate workflows, enabling administrators to consolidate and streamline configurations for better management and efficiency. | |
Workflow scheme | Identical workflow schemes | This report identifies and lists workflow schemes that have identical configurations in Jira. It helps in recognizing duplicate workflow schemes, enabling administrators to consolidate and streamline configurations for better management and efficiency. |
Health parameters of Users
Sr. no | User | Health parameter | Description |
|---|---|---|---|
User | Inactive users in Confluence for last 3 months | This report provides a list of users who have been inactive in Confluence for the past 3 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Confluence for last 6 months | This report provides a list of users who have been inactive in Confluence for the past 6 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira Product Management for last 3 months | This report provides a list of users who have been inactive in Jira Product Management for the past 3 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira Product Management for last 6 months | This report provides a list of users who have been inactive in Jira Product Management for the past 6 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira Service Management for last 3 months | This report provides a list of users who have been inactive in Jira Service Management for the past 3 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira Service Management for last 6 months | This report provides a list of users who have been inactive in Jira Service Management for the past 6 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira Software for last 3 months | This report provides a list of users who have been inactive in Jira Software for the past 3 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira Software for last 6 months | This report provides a list of users who have been inactive in Jira Software for the past 6 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira work Management for last 3 months | This report provides a list of users who have been inactive in Jira Work Management for the past 3 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. | |
User | Inactive users in Jira work Management for last 6 months | This report provides a list of users who have been inactive in Jira Work Management for the past 6 months. It helps in identifying users who may no longer need access, allowing administrators to manage user licenses and permissions more effectively. |
To download reports, Select required health parameters and click on “Download reports“
