Details

    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      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.
      Show
      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.

      Attachments

        Issue Links

          Expenses

            Activity

            Hide
            cboerema Cate Boerema added a comment -

            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!

            Show
            cboerema Cate Boerema added a comment - 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!
            Hide
            ttolstoy Theodor Tolstoy added a comment -

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

            Show
            ttolstoy Theodor Tolstoy added a comment - We see that this is blocking some features that are targeted for Q4. What is the status here?
            Hide
            cboerema Cate Boerema added a comment -

            Hi Theodor Tolstoy. Correct - this is blocking UXPROD-676 (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 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!

            Show
            cboerema Cate Boerema added a comment - Hi Theodor Tolstoy . Correct - this is blocking UXPROD-676 (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 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!
            Hide
            ttolstoy Theodor Tolstoy added a comment -

            Thank you!

            Show
            ttolstoy Theodor Tolstoy added a comment - Thank you!
            Hide
            cboerema Cate Boerema added a comment -

            Jakub Skoczen and Theodor Tolstoy, 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.

            Show
            cboerema Cate Boerema added a comment - Jakub Skoczen and Theodor Tolstoy , 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.
            Hide
            cboerema Cate Boerema added a comment -

            Jakub Skoczen and Vince Bareau 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.

            Show
            cboerema Cate Boerema added a comment - Jakub Skoczen and Vince Bareau 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.

              People

              • Assignee:
                jakub Jakub Skoczen
                Reporter:
                cboerema Cate Boerema
                Back End Estimator:
                Jakub Skoczen
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: