Repository: ietf-tools/datatracker

Issue:
WG draft "Submit to IESG for publication" workflow is infuriating
### Describe the issue

As a WG chair and shepherd of a document, once the shepherd writeup is complete I want to do two things. First, upload the writeup to the datatracker. Second, move the document into the next state.

To do step one, I navigate to the document page (e.g. https://datatracker.ietf.org/doc/draft-ietf-quic-version-negotiation/) and in the `Stream` section is a `Shepherd write-up` field with an `Edit` button that I hit, which lets me upload the doc. That all works ok, brilliant.

To do step two, I navigate to the document page and in the `Stream` section is the field WG state, that tells me "WG Consensus: Waiting for Write-up". Since I just uploaded the write-up, I want to change this state. So I press `Edit` and I'm taken to the "Change IETF WG state" page. 

![Screenshot from 2022-07-11 18-02-13](https://user-images.githubusercontent.com/6571445/178318826-e16a0233-e2c1-4a20-a40b-491492e28481.png)

The page very helpfully puts up the text `Move document to the recommended next state:` and presents a button labelled `Submitted to the IESG for publication`. When I click the button, the state updates in the dropdown box. Then I scroll down and hit the button labelled `Submit`. And it fails!

![Screenshot from 2022-07-11 17-55-18](https://user-images.githubusercontent.com/6571445/178319473-3e39fc88-89bd-41da-b343-e3073f4be9e9.png)

The error that is reported is

> You may not set the Submitted to IESG for Publication state using this form. Use the "Submit to IESG for publication" button on the document's main page instead. If that button does not appear, the document may already have IESG state. Ask your Area Director or the Secretariat for help.

The message is clear and the suggested action works. But this transition phase catches me out everytime, probably because my memory is short and I trust the datatracker to suggest useful tips to me. Instead, the datatracker suggests something that it then immediately tells me was the wrong thing to do. I'd be ever so grateful if this workflow could be improved. I have two suggestsions

1) If a different button is needed to be clicked, and you know that, just put the button on this page.
2) If you can't put the submit button on this page (for technical or other reasons) then don't suggest I waste my time doing anything else on this page. I.e. disable all the controls and just present the message in red immediately.



### Code of Conduct

- [X] I agree to follow the [IETF's Code of Conduct](https://github.com/ietf-tools/.github/blob/main/CODE_OF_CONDUCT.md)


Discussion:

Resolving patch:
diff --git a/ietf/doc/views_draft.py b/ietf/doc/views_draft.py
--- a/ietf/doc/views_draft.py
+++ b/ietf/doc/views_draft.py
@@ -1596,6 +1596,7 @@ def __init__(self, *args, **kwargs):
             if self.can_set_sub_pub:
                 f.help_text = "Only select 'Submitted to IESG for Publication' to correct errors. Use the document's main page to request publication."
             else:
+                f.queryset = f.queryset.exclude(slug='sub-pub')
                 f.help_text = "You may not set the 'Submitted to IESG for Publication' using this form - Use the document's main page to request publication."
 
         f = self.fields['tags']


Test patch: