sceeter89 / jira-client Goto Github PK

Right now you can only choose to receive all information (about updated and created issues). It would be nice to be able to choose about what events user wants to be notified.

Search tab should provide ability to filter by following fields (multi-select) which should be translated to appropriate JQL query:

• Project
• Issue type
• Priority
• Resolution

There should be some check to prevent multiple windows to appear. Right now it's being checked every 50s if pop up should appear. If first check is in 5th second of minute, then another check will fall within same minute thus second dialog.

Once I enter settings screen there is no obvious way to return. Only option is to open history dropdown and select screen below settings.

Right now, on multi display setup, dialogs appear in some random places on random screen (more or less). It would be much more intuitive and ergonomic to make them pop-up under mouse cursor.

All inter-ViewModel dependencies should be broken and integrated via message bus and every ViewModel and service should be autoregistered in IoC container.

Window prompting to log work to JIRA appears every 30 seconds.

It would be useful to store in one place recent changes that happened while application was turned on (without any persistence), so that if I see some interesting changes but do not manage to check all of them, I have an option to re-view all notifications.

Burndown chart should be available if there is some sprint selected on search screen. Chart should conform to following description: http://www.methodsandtools.com/archive/scrumburndown.php
As well some automatic comment might be generated basing on burndown chart.

Currently logs are stored in installation directory which is not too fortunate, as there won't be any logs in case user has no root privileges.

Current chars limits are too strict, and there is plenty of space to cover. Issue summary on top should be cut at 30th character, and total length of change summary line should be around 60 including changed field.

Currently the only button available in menu is export to XPS. Pivot grid should not load automatically, but only if user requests it. There should be also some button to export error report that occurred in application for easier diagnostics.

Load filter dialog - full path instead of filter name is displayed.
Save filter dialog - Missing information about what should be typed into text box
Both - It would be much more intuitive to provide button to accept instead of relaying solely on "Return" key.

Right now user receives information about all updates, not only about changes made by others. There should be some configuration option to choose whether we should exclude these changes or not.

Once dropdown is visible it doesn't stand out from rest of application. Background and borders should more clearly separate dropdown from rest of application.

Moreover these dropdowns should hide after button is clicked.

Sometimes despite having checked to skip changes made by me I receive these notifications.

In fact even if user disables prompt about updates and subscribes to unstable releases once unstable release is available confirm dialog should pop up anyway.

We want to have a report that shows number of open issues of any type drilled down by epic link. Expected visualisation is pie chart where each piece represents number of issues in given epic + one piece for issues without epic.

Popup with issue update info should contain some basic information what has changed, and if it's just status that changed then message should state that issue simply transitioned.

Currently when cards are printed, their external edges are cropped by printer. If margin was a bit larger then entire page should be printed properly.

For some reason once issue is closed epic link disappears even in Issues Browser.

Probably it will be best to use Squirrel.Windows (https://github.com/Squirrel/Squirrel.Windows)

Currently all available fields are displayed on grid which isn't neither clear nor useful. There should be also some way to view all available details of selected issue.

Right now user has to re-login to JIRA quite often. It's not to comfortable, more if session expires while app is running but ain't used then weird errors appear.

If I try to log in and configure address that is not address of JIRA instance then following message is shown:

Instead some meaningful message should be output.

It will be really useful to see amount of already logged work on given issue.

Instead of typing by hand which projects user wants to watch for changes it would be much more useful to be able to select them with some checkbox.

Probably same problem as in: #32

When user clicks "Close and update" application should automatically restart after update is completed.

When I see settings screen I can repeatedly enter settings and new screen is created every time. Once on settings screen this button should be disabled.

There should be possibility to categorize issues with colour labels. These would be assigned manually by user (or possibly automatically by providing some classifying rules - maybe with IronPython?). Then Scrum Card printer should respect labelling and provide some colourful annotations on generated XPS file.

There are problems with notification pop-ups. They do not appear everytime they should, as well it happened few times that app crashed after issue changed in watched project.

Buttons that require active connection to JIRA are enabled even when there is no such connection which can lead to errors.

If I lock my station then I miss all updates that occurred while I was away. It would be great if app waited with display until user logs in again to display all notifications.

When user opens JIRA Agile Board made for Kanban there is no point in letting her/him open sprints view.

JIRA Client should be integrated with LightShell via NuGet packages.

When user filters out some issues on "issues list" grid, then those should not be present on Scrum Cards export.

Currently plugins load takes about 7s. It would be very profitable to reduce this time.

There should be possibility to see what are bottlenecks, and how application performs. As well statistics about messages sent internally should be visible as an aggregate.

When I export issues in Issues Browser to Confluence only header for "(No epic)" is properly formatted. Others are stuck with last list item from previous epic.

For some reason content of pages is not updated. For instance: if I go to board A, then go back and choose board B, then I still see details of board A.

Currently there is only information on board page that asks user to wait. It would be much more comfortable to see what is download progress, just to be able to estimate how long download will take.

All API calls ignore flag isLast which when false (according to https://docs.atlassian.com/greenhopper/REST/cloud/#agile/1.0/board-getAllBoards) indicates that another call with incremented startAt should be performed until isLast is true.

When there are lots of issues, sometimes it happens that scrum cards are presented multiple times.

Add report showing mean, median and variance of time elapsed from issue creation to resolution.

Once new version is available and new version prompt is disabled or user chose to install on exit client should popup message that new version will be installed upon exit.

There should be separate view to draw charts basing on found issues. Firstly there should be possibility to see each members' engagement in sprint (based on story points).

Currently app assumes that story points are integer value, but in fact they are floats. So if task has value of 0.25 or 0.5 application displays it as 0.