RFE: Build reporting capability in the QUADS #271
We need to add reporting capability into quads so it can be exported and presented.
Thanks for filing this, some of this exact data will not be available to QUADS, comments in-line to address:
Located in QUADS history.
Located in QUADS history.
Strategic is not empirical data we would record, instead the best we can do is pattern match based on assignment titles and/or scrape RT information and correlate this. Humans would still need to peruse the product/portfolio and apply whatever is strategic at that time.
This data is not in QUADS, it would need to be pulled in from RT ticketing - comparing the delta of new requests across when their status label was updated (pending review, under review, approved, scheduled, in-progress). I would say that we need to automate applying RT category labels based on the request and subsequent assignment status - we're not consistent enough doing this on our own for this metric to be 100% accurate.
What constitutes configuration and turn-around time? Do you mean time for allocation/provisioning/validation and hand-off of systems?
If this is what you mean a bunch of things happen, and each system of each new assignment goes through the following:
The total time for processing all of this is probably what matters, but to record this we'll probably need to implement additional mongo collection data on a per-host basis, as well as a top-level one at the cloud level to record overall timeframe to deployment (finish time).
What is an SLO? Did you mean SLA? If so that's easy enough to determine, we aim for assignments to be available by 9:30am EDT the following Monday that they are scheduled - so exactly 15hours from the scheduled start date. Determining criteria met here would just involve comparing the start time to when the assignment is released to see if it exceeds this timeframe or not.
This is not QUADS data, it would need to be pulled in from scheduling spreadsheets and cross-referenced with the RT ticket system.
This is not QUADS data, it would need to be pulled in from the RT ticketing system. Further, we'd probably want a definitive checkbox or tick to indicate this is for a customer rather than rely on scraping free-form fields from the request.
For reference, here is the MongoDB ERD diagram of QUADS 1.1+
We'll need to discuss / design / architect both how this would look as well as a bare-minimum set of requirements and what other source(s) might be in play.
I think at a minimum we would want: