Motivation
...
Total N_REFs grouped by Workflow across all “destined to be migrated” projects, across all non-atlassian apps.
https://analytics.broadinstitute.org/JiraInspector/ProjectWorkflows?order_by=project&issue_type=hide&app=hide&app_widget=hide&project=decisions_only&jira=labopsjira&wf_component_type=hide&wf_component_type_filter=all&app_filter=non-atlassian&days_to_look_back=4000&actual_status_coverage=hideTotal N_REFs grouped by Workflow and “wf_component_type” across all “destined to be migrated” projects, across all non-atlassian apps.
https://analytics.broadinstitute.org/JiraInspector/ProjectWorkflows?order_by=project&issue_type=hide&app=hide&app_widget=hide&project=decisions_only&jira=labopsjira&wf_component_type=show&wf_component_type_filter=all&app_filter=non-atlassian&days_to_look_back=4000&actual_status_coverage=hideTotal N_REFs grouped by Workflow, “wf_component_type” and “app” across all “destined to be migrated” projects, across all non-atlassian apps.
https://analytics.broadinstitute.org/JiraInspector/ProjectWorkflows?order_by=project&issue_type=hide&app=show&app_widget=hide&project=decisions_only&jira=labopsjira&wf_component_type=show&wf_component_type_filter=all&app_filter=non-atlassian&days_to_look_back=4000&actual_status_coverage=hideTotal N_REFs grouped by Workflow, “wf_component_type”, “app” and “app_widget” across all “destined to be migrated” projects, across all non-atlassian apps.
This is one of the most granular dataset, a variety of rollups can be generated from it.
https://analytics.broadinstitute.org/JiraInspector/ProjectWorkflows?order_by=project&issue_type=hide&app=show&app_widget=show&project=decisions_only&jira=labopsjira&wf_component_type=show&wf_component_type_filter=all&app_filter=non-atlassian&days_to_look_back=4000&actual_status_coverage=hideTotal N_REFs grouped by Workflow and Apps across all “destined to be migrated” projects, across all non-atlassian apps.
https://analytics.broadinstitute.org/JiraInspector/ProjectWorkflows?order_by=project&issue_type=hide&app=show&app_widget=hide&project=decisions_only&jira=labopsjira&wf_component_type=hide&wf_component_type_filter=all&app_filter=non-atlassian&days_to_look_back=4000ProjectIssuetypesFields, non-atlassian
https://analytics.broadinstitute.org/JiraInspector/ProjectsIssuetypesFields?app_filter=non-atlassian&project=all&jira=labopsjira&format=htmlGPInfoJira datasets
...
Check the ProjectWorkflows along with IssueTypes grouped by status_coverage.
https://analytics.broadinstitute.org/JiraInspector/ProjectWorkflows?project=LCSET&workflow_name=show&issue_type=show&actual_status_coverage=show&days_to_look_back=180&jira=labopsjira&format=htmlPick a row where ACTUAL_STATUS_COVERAGE matches your interest. Slide to the right until you find the ISSUE_STEPS_TIME_MACHINE_LINK
https://analytics.broadinstitute.org/JiraInspector/IssueStepsTimeMachine?jira=labopsjira&issue=LCSET-27833&trim=LIMS Activity Stream;30
it will take you to the TimeMachine for 1 ticket of that group. You can plug in the URL other issue-keys as you see fit.the process is shown below (pls zoom in, snapshot is really big)
Caveats
Jira Inspector leverages direct access to the Oracle DB underneath, similar implementation in Cloud is not possible
...