Reporting: LDP-based Reports
(UXPROD-1319)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Reporting: LDP-based Reports |
| Type: | New Feature | Priority: | P1 |
| Reporter: | Holly Mistlebauer | Assignee: | Sharon Beltaine |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | po-mvp, reporting, team-mvp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Epic Link: | Reporting: LDP-based Reports | ||||||||
| Front End Estimate: | XXL < 30 days | ||||||||
| Front End Estimator: | Holly Mistlebauer | ||||||||
| Front-End Confidence factor: | Low | ||||||||
| Back End Estimate: | XXL < 30 days | ||||||||
| Back End Estimator: | Holly Mistlebauer | ||||||||
| Development Team: | Reporting | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||
| Rank: FLO (MVP Sum 2020): | R1 | ||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||
| Rank: hbz (TBD): | R2 | ||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||
| Rank: Leipzig (ERM Aut 2019): | R2 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||
| Description |
|
RANKING FOR APRIL 2019 GAP ANALYSIS: If your institution needs one or more of the data warehouse reports (as defined in the Reporting SIG Master Spreadsheet at https://docs.google.com/spreadsheets/d/1svUM74Dkg4KvTXLzKZK_2k_SxeukX-87NnYf8CaTrYQ/edit#gid=312878932) ready to use at your institution's Go Live date (P1), rank this feature as "go-live." The Reporting SIG will be ranking the individual reports as part of their charge. You will also see a list of data warehouse reports by clicking on the EPIC LINK above and looking at the JIRA issues linked to the EPIC. |
| Comments |
| Comment by Erin Nettifee [ 01/Apr/19 ] |
|
Are we being asked to rank if we want all the reports created, or a subset, or is there some prioritization happening? Thanks, |
| Comment by Holly Mistlebauer [ 03/Apr/19 ] |
|
Erin Nettifee the report prioritization will happen in the Reporting SIG. For the current Gap Analysis, you need to consider when you need to be able to have any reportsavailable. In other words, if you want any reports at "go live" you need to rank this feature as "go live." Hope this helps... |
| Comment by Erin Nettifee [ 03/Apr/19 ] |
|
Holly Mistlebauer - yes, that does help. Thank you. Erin |
| Comment by Sharon Beltaine [ 17/Jan/20 ] |
|
This ticket was used to organize Reporting JIRA Tickets and it has been replaced by the Report Cluster JIRA Tickets. |