The project_jump script is used to change the project state, allowing squirrels to move a project back, without explicitly clearing all pages in the previous round (we used to have a squirrel-only button on project pages, but unfortunately, while it didn't actually clear the contents of the round, it set the page states back to <round>.page_avail, which, over the years, was more confusing and potentially harmful than useful, as the reason it was implemented in the first place was no longer valid, so it was removed.
One use of project_jump that requires no database intervention, is jumping a project back from PP into F2: the page states don't change between F2 and PP, so, it's easy enough to just clear any pages needing to be cleared, without worrying about the database.
However, if a project is still in the rounds, and needs to be moved back from P2 Waiting into P1 so that a click-through-artist's pages can be cleared and re-proofed, just changing the project state is not enough, and to change the page states, it's necessary to do a direct database intervention.
Question 1: Is it a reasonable idea or a bad idea to add this functionality to project_jump? (i.e. to give the squirrel the option to set the page states to <round>.page_saved for the round the page was jumped back to.)
Question 2: How should it be designed?
The project_jump script is used to change the project state, allowing squirrels to move a project back, without explicitly clearing all pages in the previous round (we used to have a squirrel-only button on project pages, but unfortunately, while it didn't actually clear the contents of the round, it set the page states back to
<round>.page_avail, which, over the years, was more confusing and potentially harmful than useful, as the reason it was implemented in the first place was no longer valid, so it was removed.One use of project_jump that requires no database intervention, is jumping a project back from PP into F2: the page states don't change between F2 and PP, so, it's easy enough to just clear any pages needing to be cleared, without worrying about the database.
However, if a project is still in the rounds, and needs to be moved back from P2 Waiting into P1 so that a click-through-artist's pages can be cleared and re-proofed, just changing the project state is not enough, and to change the page states, it's necessary to do a direct database intervention.
Question 1: Is it a reasonable idea or a bad idea to add this functionality to project_jump? (i.e. to give the squirrel the option to set the page states to
<round>.page_savedfor the round the page was jumped back to.)Question 2: How should it be designed?