✨ Ready for publishing

[vd1992]

✨ Feature

Communicate that a pool is ready for publishing by a platform admin

🕵️ Details

Frontend, render ready to publish status for pool operator Backend, added field and the ability to update it, status accessor to output new status Policy, limited to pool operator

Update other things as needed...

🎨 Design File

Include a link to the design file (if it exists).

🧑‍🎨 Designer

Include the author of the linked design file's name (or even better, their @githubUsername) for future reference.

📸 Screenshot

Add a screenshot of the new feature (if possible).

🙋‍♀️ Proposed Implementation

Datetime field added like published_at, maybe called ready_at introduced to pool model Ready to published is ready_at < now() && published_at === null Hit the submit for publishing sets the field to current datetime

Update draft status to now require ready_at === null

✅ Acceptance Criteria

A set of assumptions which, when tested, verify that the feature was properly implemented.

• [ ] Criteria 1
• [ ] Criteria 2

[brindasasi]

@Jerryescandon do we have a figma link for this ?

[vd1992]

And for that matter, a goal? I remember we were unsure about even implementing this field hence the lack of acceptance criteria

[brindasasi]

Its not higher priority now

[brindasasi]

We can achieve the goal without introducing the new state by using notifications instead. Let's revisit after notifications have been implemented.

[tristan-orourke]

If we close or modify this ticket, consider closing #7919 and #7920