Give the user the option to open the issue in a new tab. If the setting is off, when an issue is cloned it will not open the issue in a tab. If the setting is on, when an issue is cloned it will open the issue in a new tab.

Move the Kamino button to the sidebar, above the Notifications section

When navigating to a Github issues page, the button to clone doesn't appear until after a subsequent refresh of the page.

The Personal Access Token, at a minimum, really only needs the following rights:
repo - all

The other rights were included to make sure the extension worked properly, however it has been proven that the only rights necessary are the above. Update the read me file to only call out the necessary rights.

Make the button color different than the primary green color so that it will stand out.

When the extension is installed by a user, open the Kamino github page in a tab.

The clone button appears on pull requests. This should not happen.

Whenever a clone is attempted by Kamino on an issue that has Assignees, it would return a 422 - Unprocessable Entity.

I found this out by attempting to clone an issue for testing purposes and it didn't work. Originally, I thought it might be the label or milestone but after removing those from the new issue to be created, I was still getting the same error.

I then cloned successfully another issue in the same repo that had no assignees. I then assigned myself to the issue I just successfully cloned and got the 422 error. I removed the assignee from the new issue to be created and it cloned as expected.

This bug is fixed as of commit 7bae31a and will be in version 1.7

When the issue is closed, add a comment stating:
This issue has been cloned to [org]/[repo]

Add promotional images and update existing images to make the extension look more polished and professional.

• Sometimes when redirecting to the issues list, the issue that was closed is still in the list.
• Sometimes when redirecting to the new cloned issue, the issue page doesn't yet exist.

This is due to the navigation occurring before Github's servers have a chance to resolve the actions taken by Kamino. The actions taken by Kamino are happening correctly, but the appearance is that something went wrong.

v1.5 doesn't work, have the following issues:

Popup is in the top left corner. Clicking ok doesn't work. Booooo

The JS confirm popup looks old and is ugly. Change it so that a Bootstrap modal appears for the confirmation to clone an issue.

Do not show the repository that you're cloning from in the list of repos.

User suggestion:

• I have applied filters to the issues list. Kamino does navigate back to the issues list but my filters are cleared. It would be nice if when Kamino navigated back to the issues list, it kept my filters.

I'm seeing only about 90 some repos from my org. I have a lot more. Is there an limit to the drop down repo listing for the clone to button?

When the cloned issue is created, open a new tab navigating to the new issue url

Show the top 5 most used repositories in the list first, followed by all other repos sorted alphabetically.

There are several places where code is replicated such as grabbing the url and parsing. Re-factor the code

Because the extension is updating every second to make sure the button appears on the issue page, it causes errors to be logged to the console on other pages. Add a check to make sure if there's an error due to not being on the right page, the extension doesn't continue with normal operation.

Make the stormtrooper icon a transparent png so it doesn't have the white border.

Sort the repo list by alphabet

Create a settings screen.

The only option right now should be a field for the user to enter a personal access token.

The Kamino button appears on the screen in which a new pull request is created. It also appears that the button appears twice on this screen.

User suggestion:

• The Kamino section kind of gets lost being below Milestones and above Notifications. It would be best if the section is at the very top of the side bar or at the very bottom.

keenai/windows-classic-app#291

Add a user option for Kamino to take the user back to the issues list screen of the organization for the original issue. Currently, the cloned issue is the landing spot after a clone.

When cloning, the extension should add a comment citing where the issue was cloned and that it was closed. It currently does not work.

Steps:

1. Clone an issue
2. Go back to original issue which should be cloned and closed
3. Go to issues list screen and pick another issue
4. Click the clone button

On the first click, the repo list won't appear. Clicking a second time will show the list.

Update the readme file with some instructions and what not.

Create a PR to test create bug.

Also found some issues with the previous bug fixes

There are scenarios in which the extension will render the clone button multiple times on the issues screen. The extension code should check to make sure the button doesn't already exist before appending to the DOM.

Make the settings screen look good.

Alter the clone button to be a split button in which the left side of the button will clone the issue to the last used repo and the right side of the button will be the usual drop down

Whenever the page is partially refreshed, for example, when the issue goes from closed to open, the clone button is wiped out and the page has to be refreshed in order for the button to re-appear.

Try putting the button on the same row as the other buttons to see if this resolves the problem.

When Kamino clones an issue, there's no reference as to who created the issue originally. It would be nice to have the creator listed in the cloned issue's description.

When Kamino is used to close an issue, the comment should say:
Kamino closed and cloned this issue to org/repo so that members know that the issue was moved using a Chrome Extension.

Repositories with a name that contains a . do not work when trying to clone.

The length of the quick clone button can be long due to the length of the repo name. Make the button length a static width and overflow the repo name with ellipsis

Also make sure button says Clone to instead of Clone issue to

Applied filters has an issue in which the filters aren't being cleared when looking at different repositories. Also, if you are searching for something in the Search box, this ends up being applied to the issue filter and it should not.