kamino icon indicating copy to clipboard operation
kamino copied to clipboard

Ability to sort issues by labels

Open Daksh777 opened this issue 3 years ago • 8 comments

Is your feature request related to a problem? Please describe. I want to clone issues only with the bug label, it's not possible to batch clone it but only do it one by one by using the issue search filter

Describe the solution you'd like Ability to sort issues by labels and then batch clone them.

Describe alternatives you've considered None

Additional context None

Daksh777 avatar Jun 09 '21 11:06 Daksh777

@all-contributors please add @Daksh777 for ideas

johnmurphy01 avatar Jun 09 '21 12:06 johnmurphy01

@johnmurphy01

I've put up a pull request to add @Daksh777! :tada:

allcontributors[bot] avatar Jun 09 '21 12:06 allcontributors[bot]

@Daksh777 a good feature request. For the batch clone, we could add a filter/search based on the labels in the repo you are trying to clone from.

johnmurphy01 avatar Jun 09 '21 12:06 johnmurphy01

@Daksh777 a good feature request. For the batch clone, we could add a filter/search based on the labels in the repo you are trying to clone from.

I'm unaware of the complexity but how about using the issue search itself and then cloning the issues which are selected/checked and have a button to clone selection? image

Daksh777 avatar Jun 09 '21 12:06 Daksh777

An interesting idea. That's a good approach, the only problem I see is that it would involve a lot more querying of Github's DOM which is not guaranteed to always stay the same as they make updates/changes to their web application.

Building my own UI for filtering and selection guarantees that it will always work unless I personally introduce a bug.

But let me think about this and if anyone else has input, feel free to comment here. I do agree this would be more intuitive and really mesh well with the existing UI.

johnmurphy01 avatar Jun 09 '21 13:06 johnmurphy01

Although GitHub hasn't made changes so significant which changes the UI completely in the past (sorry if I'm wrong, I haven't been very long on GitHub), it's better to prefer long time compatibility than integrating it in the UI which may or may not change in the future, and if it does, your work gets wasted. So I'm going to vote for building your own UI, even though it's not so well integrated.

Off-topic message

Thank you so much for adding me to the contributor's list and also following me, I really really appreciate that as a beginner in this field 😄.

Daksh777 avatar Jun 09 '21 13:06 Daksh777

No problem! And thanks for your input. We can always begin by adding the filter/search into my UI and if there's a lot of demand, I can look into integrating the functionality more tightly into Github's UI.

johnmurphy01 avatar Jun 09 '21 13:06 johnmurphy01

Piggybacking on this issue:

I will appreciate if we could somehow determine the order of issues cloned.

I want to use Kamino to batch clone issues from a template repository to new repositories created from that template. When I batch clone, the order of issues are reversed:

Screen Shot 2021-06-26 at 22 08 55

Keeping the order of issues is really important for me because each issue represent an assignment in my use case and assignments needs to be done in an order.

Btw, thanks for implementing batch clone feature, it looks really good! 🎉

safaorhan avatar Jun 26 '21 19:06 safaorhan