thsaravana / issue-tracker-idea-plugin Goto Github PK

If no repository is mapped, then in the Empty Screen show "No Issue management configured. Configure". The last should be a hyperlink which ll go to Settings - Tasks - Servers ..

Add the following additional Information to the ToolWindow:

1. An extra column for the Table to show the Type of Repository (Github, GitLabs, Bitbucket...)
2. Show the Url to the particular issue in the Summary pane

We will load about 20 issues for the first time, then when the end of the list is reached, we will load another 10 and then 10 and so on. If there is no more issues to load, then we will stop loading.

Write the API for the calls to be made from the Plugin

Add a toolbar to the toolwindow and add a 'Refresh' button to it. Do necessary refactoring to get this done properly

1. Show progress indicator when the initial issue list is getting populated.
2. Show progress indicator in the Summary panel when Comments is getting loaded

Currently when we open multiple projects in multiple windows, then clicking on "Show Details" in one Window influences all the Windows opened. Issue Tracker ToolWindow should be Project specific.

CheckTask is no longer necessary. So remove that.

Write action to Create a Task (changelist in VersionControl) from the Selected issue in the Issues Table. Create a toolbar action and a popup action as well.

Create a panel with list view to show the list of issues. This will be the base version, so just populating the list should be sufficient. Searching/Starring can be done in the next version.

Add the action to Show or Hide the Summary Panel. Give it an appropriate Icon, like the one in "Version Control" plugin.

When the Issue Tracker tool window is first open, don't directly load the issues from the server. First try to see if there is something available in the cache. If not, then and only then load issues from server.

Let's not mingle the UI with the content.
So create a simple API to fetch the Issues, fetch specific information of an issue, so on... This way, the api itself should be testable without the need of the UI.

Except the Refresh action, all other actions are Issue specific. So in addition to the Actions being the Toolbar of the ToolWindow, expose them as Right Click options as well. So when the user right clicks a particular issue, he should see all the actions there as a pop up.

Refer: PopupHandler.installPopupHandler(myList, popupActions, ActionPlaces.UPDATE_POPUP, ActionManager.getInstance()); in VcsSelectionHistoryDialog.java

The Summary panel is fully HTML and yet it appears so plain. Make it good looking, so that people would actually use it, rather than mock it :)

1. Give the Description a background color (till the end, full right) with left, top, bottom padding of 5px or so.
2. Then Keep the same format for Comments, but just indent it a litter further, so that it appears hierarchically beneath the Description
3. Finally show the IssueUrl section as a Round cornered button with an appropriate color, with the url as hyperlinked text.

Currently we are showing all issues. But this may no always work. So we need to provide option to search for issues (from the server) and then publish that in the IssuesPanel (as well as add to the synced list if it's not present), but not lose the full issues that we might have synced. Once the Search query is cleared, we will show the Full issues that we have already synced. This means we need a Cache mechanism.

Add an Action to ToolWindow so that it opens the IssueUrl in the broswer. If no issue is selected, then disable the action.

Use the Comment.appendTo() method to show the Comments. This way we get the Profile Pic if some repositories support them. See screen shot.

Perform syncing operation in background using a ProgressIndicator. Do not block the Main thread.

Right now the Icon for Tool Window is the HockeyApp icon. Replace that with a nice cool icon.

When an issue is selected, we should show the detailed info about that issue, like the creation date, description, comments, etc... How we are going to show this is still not decided. Probably in an extra tab to the existing panel?

Right now, the icon of OpenIssueInBrowserAction is the Web icon. This remains same for all the repositories. It stays same for GitHub, Bitbucket, etc... The same goes for the text as well. It says "Open issue in Browser".

Instead of this, make this more reactive and repository specific, if the selected issue is of GitHub repository, then show the GitHub repository icon and the text "Open in GitHub".