Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create Setting for Default Repository per Channel for Creating Issues #611

Open
brian-hayward opened this issue Nov 18, 2022 · 4 comments · May be fixed by #806
Open

Create Setting for Default Repository per Channel for Creating Issues #611

brian-hayward opened this issue Nov 18, 2022 · 4 comments · May be fixed by #806
Labels
Type/Enhancement New feature or improvement of existing feature
Milestone
v2.4.0

Comments

@brian-hayward
Copy link

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
Copy link
Contributor

@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?

@Kshitij-Katiyar Kshitij-Katiyar added the Type/Enhancement New feature or improvement of existing feature label Oct 5, 2023
@mickmister
Copy link
Contributor

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
Copy link
Contributor

hanzei commented Oct 10, 2023

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
Copy link
Contributor

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

@raghavaggarwal2308 raghavaggarwal2308 added this to the v2.4.0 milestone Jul 9, 2024
@Kshitij-Katiyar Kshitij-Katiyar linked a pull request Jul 17, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type/Enhancement New feature or improvement of existing feature
Projects
None yet
Milestone
v2.4.0
5 participants
@mickmister @hanzei @raghavaggarwal2308 @Kshitij-Katiyar @brian-hayward