Page History

I expect to be able to publish an AV if it is read only and not currently published to a place. 9.27.24

FS and SS should appear after an import. It currently needs a hard refresh to show them 9.26.24

ATMs should keep their Facility Configs unless actually modified by the user. 9.27.24 still see this

Also hardrefresh is back on Pressure Plots after configuring an ATM

This was done in Sprint 87 after other changes.

Entering Time Ranges and Duration in Time Reservations needs the Time Bins code brought to the FE. i think this works not. 9.27.24

Publishing and Prioritizing an AV should not depend on the read only state of the ATMV 10.1.24

If AVs and ATMVs are in the side by side panel view, a change to the OSD's SP should push a change to the pressure plot to have active feedback. 9.27.24

9.26.24 - badge appears without a refresh on publication

badge needs a refresh after cloning still

done. 9.27.24

9.26.24 - fixed - publishing an AV with an ATMV sets the ATMV to read only and the badge appears

Cloning an ATMV sets it to read only and the badge appears without a refresh

9.26.24 - publication destination names updated in PTools

9.26.24 - publication destination names in resources tab's names updated

9.27.24

9.27.24

9.27.24

9.27.24

9.26.24 - fixed. The save and delete buttons are hidden if the ATMV is read only

9.27.24

9.27.24

9.27.24 - Not a fan of where the Time Reservation tooltip is. See STT-2106

Upload a Time Reservation and Facility config should be persisted. 9.27.24

make the UI cleaner when no ATMs exist on an ATMV.

9.30.24 If no ATM exists, UI goes immediately into making an ATM

got fixed else where along the way.

10.1.24

10.1.24 apparently was fixed along with 2054 though we're not sure how

10.2.24

10.2.24

10.2.24

10.2.24

10.2.24

10.3.24

10.3.24

10.4.24

10.4.24 - something isn't quite right but I'll wait for Jen's merge for STT-2090 to hit

10.8.24 I think

10.4.24 FPO bits but that's okay

10.8.24 done

I expect to see Time Reservation and OSDs on pressure plots when this is done. The labels should be dynamically populated on the pressure plot. I should be able to see the plot without selecting an AV (i.e.,g no OSDs). Facility Configurations are respected by OSDs and Time Reservations; dates are not longer enforced for Time Reservations either.

I should be able to make changes to the scheduling priority for OSDs and that show up on the Pressure plot. 9.16.24 yes but there are remaining hardcoded labels

Time Reservation UI should be more informative for a general user. 9.18.24 - mostly done but the duration validation doesn't wrap around 24. I cannot reproduce the wrap around issue now. I think it is fixed.

I expect not to be able to save an ATM without specifying a Facility Configuration if applicable and the default should be Any. 9.16.24 I don't see this

9.18.24 The default is any and there is no way to not select something.

FE should disable fields in ATMV if it is read only. separate ticket for disabling save and delete button

There should be feedback in the simulation suite for successful uses of the simulate allocate and approval buttons.

Simulate Allocate and Approve functions should check that a published AV exists for each facility instead of just 1 existing.

Something is broken here - booted down

Prioritize should not be functional if the AV is read only

I should be able to publish an AV if it is not published elsewhere. 9/24/24 still present booted for next sprint

This seems to only be a local problem and not present on Dev/Test

I should be able to download the chart data in the Resources tab

Now that scheduling priorities can be updated, I should see that reflected on the many subheadings in the ui. 9.16.24

BE biz - I don't test this

The scheduler tools should not ask for a PDG in PPR (ever) but currently will if Finalize Configuration is not done.

The gate was incorrectly set to End of Consensus instead of Finalize Review Configuration - fixed

Prioritization Tools name in coming

In an AV, the proposals were showing up multiple times. 9.16.24 fixed

Done as part of 2020

Done but there's a hard refresh bug in time reservations STT-2079

Done but there's a hard refresh bug in time reservation STT-2079

We now dump the cache whenever a change is made to TR. It looks like using the simulation suite acts weird through. I ran into hard refreshes there when I hand made ATMs.

Each pressure plot should only have labels associated with Time Reservations that are actually on that pressure plot instead of all possible labels - only ones that are ``applicable to me''; This works except for cases of Any - new ticket in STT-2081

This is a cute bug. Making a second ATM updates the facility configuration of the first one, at least in the FE.

Fixed with another ticket

It was gone but now it is back and it works.

This was done a while ago with the addition of the facility configuration. Not sure why it is only now showing up in the sprint.

We decided after STT-2026 that this is not actually a bug. It was our understanding that was wrong.

I believe this is there now but the FE needs updated to match some of this. The newly made file importer should then also refactor.

At the end of this ticket, I expect to be able to upload a file with Time Reservations. but - it is quite ridged.

See ticket for further notes.

Discussion to assess version goal. Many stories already written, future features noted in ticket.

The AV log is being updated properly. The ATMV log does not say it was unpublished. They should probably have consistent behavior.

Using the simulation suite to publish for place should result in a published AV per facility for the place if and only if one does not already exist for publication to that place. Testing 9/9/24 showed this mostly works but it is ignoring all facilities if any facility has a publish to place

When saving Time Reservations, there is an error but it seems to save. They do not seem to affect the pressure plot though.

I am also getting a error when I publish (though it still works)A backend error occurred at 'api/timebins?available_time_model_version_id=1' : Internal Server Error The server encountered an unexpected internal server error (generated by waitress)I get the error in the resources tab too. Done as part of 2005.

 BE work

 As part of 2024

8.23.24 - This works as expected - a comment is generated following a pattern for each of the 6 Proposal Disposition comment fields. It happens when the "publish to closeout" is done or the "advance to end of allocate and approve".

8.23.24 this works - it creates a new ATMV if one doesn't exist and a new AV and publishes to approval. It does publish the Disposition AV though, which is not desired. Bug ticket made. STT-2021

8.23.24 this works like 1792 but it unpublishes the Disposition AV. Bug ticket made. STT-2021

8.23.24 this works but it unpublishes the Disposition and Approval ones; it also duplicates a Closeout publish. Bug ticket made. STT-2022

8.26.24 The generate comments and scores now works on external UI. I also see the comments in the Consensus UI/ Proposal Review.

8.26.24 I believe this works now. I think testing it more would be good though. It now ensures that duplicate Primary and Secondaries are not assigned even if the external review is given the primary slot.

8.26.24 the OSR list now shows the proposal state instead of just a place holder of "Submitted".

8.26.24  Fixed the bug

8.26.24 Fixed the bug

Facility Configurations for VLA are all defaulted to "Any" when an Observation Specification is generated by both the simulation suite and the manual proposal creation.

cannot test until stt-1976; which is FE

I expect to be able to set a seed when generating a test or demo solicitation and it produce the same data sequence each time a solicitation is generated with the same seed.

7.23.24 - This works as expected.

I expect that when I try to publish an AV and go to select an ATMV, I will be prevented from publishing if no ATM exists on the ATMV. 7.19

I except the read_only flag to be respected on ATMVs so I should not be able to add/delete/modify any ATM or Time Reservation. I should be able to change the comments, clone, and send for publishing with any AV.

Test-

• The BE respects boolean on ATM updates - yes 7.19
• The FE respects boolean on ATM and prevents  modifications (disabled text field) - no 7.19  (split to STT-1962)
• The BE prevents updates to Time Reservations - no 7.19 - yes 7.24
• The FE prevents modification to TRs - no 7.19 (split to STT-1962)

Works as expected 7.26

 improvements for future work identified

Not that I can test it

No UI component, dependent on later work 1978

No UI component, dependent on later work 1978

No UI component, dependent on later work 1978

5/24/24

I can make multiple allocation requests now.

5/24/24

This seems to work now.

5/16/24

Cloning isn't setting the parent version to read-only

cannot test

• version history of parent version is updated with a time stamp of when it was cloned (can we add the allocation version number of cloned?)
• version history of cloned version is updated to reflect what parent version spawned it and a timestamp

Daniel says the log history should work but it doesn't seem to be. 

It now works, though there's an extra item being displayed on the AV row.

I made a ticket for respecting the read only. Also found that a hard refresh is required to show the read only badge.

until the new publishing endpoint is connected with the FE, this ticket cannot be further tested. Luckily it worked when I could test it. 5/15

until the new publishing endpoint is connected with the FE, this ticket cannot be further tested. Luckily it worked when I could test it. 5/15

until the new publishing endpoint is connected with the FE, this ticket cannot be further tested. Luckily it worked when I could test it. 5/15

until the new publishing endpoint is connected with the FE, this ticket cannot be further tested. Luckily it worked when I could test it. 5/15

I see the history of publication now. And when I publish another version, I see that the log history is updated.

this "works" but the data it is comparing is from solicitations, not allocation versions - Reid says that needs a refactor. STT-1917 pending.

There's some obvious refinement needed but this works. It doesn't apply to the pressure plot or facility reports yet. that is another story. 

N/A

This still appears when adding a new ATM but that is outside the scope of the ticket as we need to delink pressure plots and facility reports.

this was done as part of  STT-1823