Create Setting for Default Repository per Channel for Creating Issues

[brian-hayward]

Mattermost channels are often organized by team, which in turn are often organized by functional area. In this case, they usually end up creating issues in the same repository. However, right now, you have to search for the relevant repository every time you create an issue, which can be very painful depending on which letter your repo starts with (the list is alphabetical) and how many repos your org has.

It would be very beneficial to make repository selection easier. I could see this happening in a few different ways:

1. Create a default repo setting (probably the easier of the options) and have this auto-filled in the pop-up window.
2. Put the most recently selected repos at the top op of the list (functionally helpful, but more complicated to implement)
3. Create an allow list of repos that could be selected from a channel (more granular control, but more limited use cases and maybe unnecessarily restrictive)

Right now, I would prefer option 1.

[Kshitij-Katiyar]

@mickmister @hanzei What do you think about this feature we already have a system configuration setting for selecting and defaulting to an organization. Should we also create a setting for the repo as well?

[mickmister]

What do you think about this feature we already have a system configuration setting for selecting and defaulting to an organization. Should we also create a setting for the repo as well?

@Kshitij-Katiyar The request is to have this scoped per-channel, so setting a global default repo doesn't really help here. I'm thinking we can implement this by running /github default-repo mattermost/mattermost-plugin-github. Then we'll store that repo name for the current channel in the KV store.

[hanzei]

Let me throw in an alternative option: Does it make sense to put the repos for which a subscription exists in a channel on top of the selection list in the issue modal? The assumption is that subscribed repos are the ones that uses of the channel care about.

[Kshitij-Katiyar]

@mickmister @hanzei Both approaches look good to me as one is a new feature and the other is just an extension.