Requests (UXPROD-790)

[UXPROD-1613] Disallow Requests by Inactive Users Created: 21/Mar/19  Updated: 16/Sep/20  Resolved: 24/Oct/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
Parent: Requests

Type: New Feature Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: cap-mvp, requests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Defines
is defined by CIRC-445 Disallow Request by Inactive User Closed
is defined by UIREQ-319 Disallow requests by inactive users Closed
Potential Workaround: CPT: No workaround, so we added this to the MVP. Would be a defect if not included.
Epic Link: Requests
Front-End Confidence factor: High
Back End Estimate: Small < 3 days
Back End Estimator: Martin Tran
Estimation Notes and Assumptions: Back-end note: The user's active status is already in the area of the code that we can implement validation. We just have to add this check to the request processing process.
Development Team: Prokopovych
PO Rank: 72
PO Ranking Note: 2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
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): R1
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): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R4

 Description   

Disallow requests by inactive users



 Comments   
Comment by Cate Boerema (Inactive) [ 21/Mar/19 ]

Adding Chalmers ranking according to a comment from the user story

Comment by Cate Boerema (Inactive) [ 15/May/19 ]

Martin Tran I am spreading the estimation requests around the CF team devs. Do you think you could estimate this one for me

Comment by Martin Tran [ 15/May/19 ]

Cate Boerema It'd be at most 3 points, include testing, but could be 2.

Comment by Cate Boerema (Inactive) [ 16/May/19 ]

Thanks Martin Tran! Since this is a feature, we actually need t-shirt size estimates. Could you please fill out the back end estimate and back end estimator field? Here's a screenshot from another UXPROD feature:

Generated at Fri Feb 09 00:17:01 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.