Allow adding organisers during workshop creation

[biggianteye]

Description of the issue 📄

When you create a workshop, you cannot set who is going to be running that workshop. You have to first create it and then edit it to be able to manage organisers. It would be good to be able to set everything up in one go.

Screenshots 📷

The interface when you create a workshop. No "Organisers" field.

The interface when you edit a workshop. The "Organisers" field is visible.

Steps to fix 🛠

Make the Organisers visible as part of creating a workshop.

To do 📋

• Claim this issue (comment below, or assign yourself if you are part of the codebar org)
• Fork and clone the repository
• Update the relevant files. Follow the steps to fix section in this issue.
• Commit your changes as one commit. Use the title of this issue as your commit message
• Submit a pull request
• Mention this issue in the PR description by including it's number
• Have your pull request reviewed & merged by a codebar team member

[mikej]

I think the reason why this works this way is because when adding a workshop we don't know the list of valid organisers until the chapter has been selected.

So at the moment what we do is allow a chapter to be selected when adding a workshop and then on saving the workshop we set the organisers to be all of the current organisers for that workshop's chapter. And then if that list needs to be adjusted then organisers can be removed by editing the workshop once it has been saved and linked to the chapter.

There are a couple of different places where we provide a link to create a new workshop so one possibility is that when creating a workshop from a particular chapter's admin page then we could set the chapter on the workshop to be that chapter and pre-populate with the organisers from the chapter. We'd then be able to show the organisers field on the new workshop form to enable that list of organisers to be adjusted as required.

e.g. for Manchester:

That "New workshop" button currently links to /admin/workshops/new but we could pass a query parameter to set the chapter to the page's chapter.

That would likely be more straightforward than dynamically updating the list of available organisers on the form based on changes to the chapter dropdown.

Other contexts where a workshop can be outside outside of the page for a specific chapter could continue to work as they do now.

[gnclmorais]

That "New workshop" button currently links to /admin/workshops/new but we could pass a query parameter to set the chapter to the page's chapter.

I came here to suggest the same thing; with a ?chapter_id=<number> argument, we could load that chapter, hide the chapter selection dropdown, and show the organiser dropdown instead. Thoughts?