Workflow Services (Back End for Workflows and More)
(UXPROD-593)
|
|
| 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: |
|
||||||||||||||||||||
| 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. |
| Comment by Cate Boerema (Inactive) [ 17/Oct/18 ] |
|
Hi Theodor Tolstoy (One-Group.se). Correct - this is blocking
My current assumption is that we will only make partial progress on
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. |