Skip to end of banner
Go to start of banner

Organizing Reporting JIRA Issues

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »


INSTRUCTIONS


Entering UXPROD Issues for Reporting Clusters:

  • The po-mvp label needs to be added to all issues that are to be included in the MVP ("po-mvp" = Q4 2019 = January 1, 2020); "Go Live" issues should be targeted for the January release date to allow for 6 months of testing prior to a given institution actually implementing FOLIO as their LMS in Summer 2020
  • Features need to have the PO Rank field assigned by Nassib; this field ranking must be unique within Epic; Ranking is lowest (0) to highest (120)
  • For Back-End Estimate, all of the features must have a tee-shirt size estimate assigned to them; biggest T-shirt size, XXL, is 30 days; issues bigger than  30 days must be broken into smaller components; for now, use the XXL 30 days setting on all Reporting Clusters
  • All issues have Developer set to "Reporting LDP"
  • All issues must have the Epic link populated
  • Reporting Cluster UXPROD issues need to
    • be linked to the Reporting: LDP Reports Epic, UXPROD-1319
    • be linked as "related to" to all the REP-XXX issues associated with that cluster
    • include the labels "cluster" and "reporting" 
    • be assigned to Nassib Nassar


NOTES


Clusters:

How to organize clustering in JIRA?

  • linking?
  • labels?
  • create a cluster issue and link clustered reports to this one issue?
  • create UXPRODs for clusters?

Example

UXPROD-1234 Collections Use Cluster - gets ranked, must be under an EPIC

-one or more queries indiv JIRAs

  • REP-103
    • is satisfied by UXPROD-1234
  • REP-104 first quarter
  • REP-107 up to a year


------


UXPROD-1234 Coll Use Cluster - gets rank, but no work done here

  • link to REP 567 (original requirements)
    • link to RQ 123 report query
    • link to RDM report data model


JIRA Projects

  • Report Queries - lists all report queries
    • RQ 123 (task)
    • RQ 345 (task)
    • etc
  • Report Data Models
    • RDM 333 (tasks)
    • RDM 444 (tasks)









-----


EPICs:

UXPROD-1128 - LDP Alpha 1 - July 2020 (rank = go live)

-review and change to January 2020? rename?

UXPROD-1881 - LDP Alpha 2 - October 2020 (rank = up to a quarter after go live)

UXPROD-1882 - LDP Beta - April 2021 (no ranking)

UXPROD-1901 - LDP 1.0 - July 2021 (rank = up to a year after go live)


Blockers:

UXPROD-1438: Process for tracking data-related API schema changes

UXPROD-1431: Data attributes needed for reporting

UXPROD-1414: Complete documentation of data attributes in module APIs

FOLIO-1839: Enable incremental requests for all records since last request


Labels

LabelDefinition
ldp-platformreporting functionality feature; not a report
personal inforeport that uses personal information impacting GDPR data privacy compliance
external statisticsreport in the functional category of external statistics
resource accessreport in the functional category of resource access
resource managementreport in the functional category of resource management
user managementreport in the functional category of user management
consortiareport requirement from Consortia
NFRnon-functional requirement that is mandatory
mandatoryfunctional (business process) requirement that is mandatory
  • No labels