Cloning simplenws issue copies sending status

Thank you very much! This module together with this patch makes my life so much easier.

Is this feature needed? Would the "Exclusion list" options in Quick Node Clone's settings work, to exclude cloning the simplenews_issue field?

The exclusion list options in quick node Clone's settings don't currently concern simplenew_issue field.
Without the patch, quick node clone module can't really be used with simplenews issues.
If this patch could be added in the module, it would be great !

Add a checkbox concerning simplenew_issue field in the module settings doesn't seem useful because I don't think anyone would want to create a simplenews that would be considered already sent.

The exclusion list options in quick node Clone's settings don't currently concern simplenew_issue field.

I am sorry. I don't understand. Does the exclusion list not work for simplenew_issue?

You are right, the field is in the exclusion list (the wording misled me).
So no need for this patch, very sorry for the inconvenience.

I can confirm that the solution proposed here fixes the problem:

1. Under "Exclusion list" > "Entity Types", check "Newsletter Issue"
2. Under "Fields" > "simplenews_issue", check "Newsletter"

If you now clone an already sent Simplenews newsletter, you need to select a Newsletter, the "Sent"-value is not carried over, and the cloned newsletter can be send (the "Send now" button is present).

This is probably something all Simplenews and Quick Node Clone users will experience ... Is a mention on the project page or in the README worth considering?