Workflow Services (Back End for Workflows and More) (UXPROD-593)

[UXPROD-594] Scheduler Created: 22/May/18  Updated: 03/May/22  Resolved: 02/Apr/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Workflow Services (Back End for Workflows and More)

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Jakub Skoczen
Resolution: Won't Do Votes: 0
Labels: automation_and_workflows, core, mandatory, sprint45
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-1445 SPIKE: Decide on scheduling approach ... Open
relates to UXPROD-949 Rewrite Cornell's Web based LS-Tools Closed
relates to CIRC-132 Backend Work for UICIRC-54: Anonymize... Closed
relates to OKAPI-969 API for Okapi timer task management Closed
Epic Link: Workflow Services (Back End for Workflows and More)
Front End Estimate: Medium < 5 days
Front-End Confidence factor: Low
Back End Estimate: Large < 10 days
Back End Estimator: Jakub Skoczen
Estimation Notes and Assumptions: This item stands independent from the core WE service as there are no-WE features that call for this functionality (timed status transitions from Recently Returned to Available, Patron Notice triggers, User/Proxy inactivation due to expiration, etc). The architecture, however, is unclear thus low confidence.

 Comments   
Comment by Cate Boerema (Inactive) [ 03/Jul/18 ]

Hi Jakub Skoczen, I was just going through the list of featured targeted for the Q2 release and saw that this one still had the status of Open (as opposed to Closed). Are you expecting this to be in or out for the Q2 release? If not, can you please change the fix version accordingly? If so, the status should probably change. Thanks!

Comment by Theodor Tolstoy (One-Group.se) [ 16/Oct/18 ]

We see that this is blocking some features that are targeted for Q4.
What is the status here?

Comment by Cate Boerema (Inactive) [ 17/Oct/18 ]

Hi Theodor Tolstoy (One-Group.se). Correct - this is blocking UXPROD-676 Closed (Setup/configure patron notice logic (Patron Notices Policies) which we recently targeted for Q4, as it will be assinged to Vega.

My current assumption is that we will only make partial progress on UXPROD-676 Closed in Q4. There will be aspects that have to wait to Q1, due to Scheduler and the fact that the stories aren't yet ready (leaving less time for development).

Jakub Skoczen and I will be talking about NFR prioritization later today and this will definitely come up. We'll update this issue when we know more!

Comment by Theodor Tolstoy (One-Group.se) [ 17/Oct/18 ]

Thank you!

Comment by Cate Boerema (Inactive) [ 08/Nov/18 ]

Jakub Skoczen and Theodor Tolstoy (One-Group.se), I am marking this as needed by Chalmers to go-live to give it more visibility than it currently has (particularly on the Q4 Weekly Status Report - Chalmers section). This is a "mandatory" feature which means we haven't asked for early implementer rankings. That said, it is a critical piece of blocking infrastructure that is needed for many things Chalmers needs to go live. The fact that is hasn't been started is a major concern and I want it to be more visible in our chart.

Comment by Cate Boerema (Inactive) [ 04/Dec/18 ]

Jakub Skoczen and VBar have decided this feature is not needed after all. Rather than building a shared Scheduler component, modules will build in the necessary scheduling functionality natively. Removing this from Q1 2019. I'll let Jakub Skoczen refactor or close this feature as he sees fit.

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