Motivation
Over the years our LabOpsJira has been extended with a multitude of projects, workflows, issue-types, custom-fields, etc. Regardless of where our new Jira home would be (Atlassian Cloud or DataCenter), at some point we will have to conduct a User Acceptance Tests (UAT) to make sure that crucial functionality is not affected. These UATs would be very tightly linked to a specific project/workflow (for example: LCSET tests would look very differently from PDO tests). Given the variety of projects, collective knowledge is mostly stored in people’s minds. So just brainstorming with multiple teams about “what the current projects/workflows are and who is doing what” will not be very productive.
We need a deep Analytics off Jira itself which could provide a complete picture of active project diagrams, issue-types, workflows, users, transitions, LIMS interactions and more.
Having done such exploration upfront, 3POs
would be able to target the most important projects/workflows 1st (resp. prioritize over time),
would know which team to contact (along with specific names)
would have a project/workflow diagram printout at hand along with specific issue-examples to drive the discussion
Discussions with LOJ teams would become a data-driven workshop making sure that all bases are covered.
ProjectWorkflows - see all issueTypes/workflows for a given project
how massive a project/workflow is (N_issues)
is it current or outdated
print out the generic workflow diagram
get representative issue tickets to drill further via IssueStepsTimeMachine tool
use these params to show or hide a specific field:
workflow_name=show|hide
issue_type=show|hide
how far in the past to look: days_to_look_back=180
which Jira instance: jira=labopsjira|gpinfojira
project to look into: project=LCSET (all also works
)do you want to look into the browser or download to CSV: format=html|csv
IssueStepsTimeMachine - look at all the steps a given ticket has gone through. Nice start for drafting a UAT (user acceptance test)
who did what and when ?
status transitions, issue-links, resolutions, etc
Lab manual steps as well as automated LIMS steps (shown as user 'squid'). Test-plans will have to include intertwined steps from both
which Jira instance: jira=labopsjira|gpinfojira
format=html|csv
remove clutter - some fields (like “LIMS Activity Stream” posts from Mercury) could be a distraction
https://analytics.broadinstitute.org/JiraInspector/IssueStepsTimeMachine?issue=LCSET-27304&jira=labopsjira&format=html
Then add the trim=LIMS Activity Stream;30 param (or add a bigger trim-number if you feel adventurous)
https://analytics.broadinstitute.org/JiraInspector/IssueStepsTimeMachine?issue=LCSET-27304&jira=labopsjira&format=html&trim=LIMS Activity Stream;30
ActiveUsers - users who have logged-in or created in the past N days
how far in the past to look: days_to_look_back=180
which Jira instance: jira=labopsjira|gpinfojira
format=html|csv
ProjectLinksOverview - how projects are interlinked (last 30days worth of links)
which Jira instance: jira=labopsjira|gpinfojira
project to look into: project=LCSET (all also works)
ProjectAppDependencies - how much each project is infected with apps (validators,post-functions,etc)
how far in the past to look: days_to_look_back=1000
which Jira instance: jira=labopsjira|gpinfojira
how much a given project is affected by apps: order_by=project
how much of an impact a given app has across projects: order_by=app
Caveats
Jira Inspector leverages direct access to the Oracle DB underneath, similar implementation in Cloud is not possible