[UX] Inadequate fields keep visible when Published is set to Yes or No

[andersonjeccel]

This one is tricky.

First problem

When a resource, like an email, is being created and set Published to Yes, the field "Publish at" keeps visible. It doesn't make sense to schedule to publish something that's already published.

How to reproduce:

1. Open Channels > Emails
2. Create new
3. Set Published to Yes
4. The "Publish at (date/time)" field keeps visible

Expected result

When Published is set to Yes, the field "Publish at (date/time)" should be hidden.

---

Second problem

When Published is set to No, the field "Unpublish at (date/time)" keeps visible. Why to schedule to unpublished something already unpublished?

How to reproduce:

1. Open Channels > Emails
2. Create new
3. Set Published to No
4. The "Unpublish at (date/time)" field keeps visible

Expected result

When Published is set to No, the field "Unpublish at (date/time)" should be hidden.

---

Care about this issue? Want to get it resolved sooner? If you are a member of Mautic, you can add some funds to the Bounties Project so that the person who completes this task can claim those funds once it is merged by a member of the core team! Read the docs here.