changhaitravis / foresight Goto Github PK

We may wish to limit a project dependency graph's ability to traverse depencency trees belonging to other projects. Or perhaps make this behavior optional.

Allow users to set their own custom colors for the Issue Types that exist on their system.

Use JIRA's Active Objects to store and retrieve these along with other user settings we come up with.

https://developer.atlassian.com/docs/atlassian-platform-common-components/active-objects/getting-started-with-active-objects

As per user request, selecting which relationship types are included in the graph may be helpful since there are plugins that add different relationship types, or someone may be interested only in cleaning up duplicates.

JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

When viewing issue from "View all issues" pane, D3 force directed graph is not generated and fails with the above error.

Inward edges to enlarged r=14 Circles signifying "This Issue"
In Issue tab view have their Arrow tips now within the circle.
It's now not evident as to what is the directionality for these edges.

As you can see, at the current size, I can display 7 before the legend surpasses the width of the canvas.

Issue lost until the next refresh if you accidentally drag and drop it outside of the bounds of the canvas.

Maybe there's a way to detect circle out of bounds and float back into the window. Or perhaps prevent circles from being dropped out of bounds in the first place?

D3's force directed graph becomes slow even on a powerful CPU once it passes over 300 nodes.
It may be time to switch to a WebGL render.

Hopefully PathGL http://pathgl.com supports D3's force directed graphs.

Create a button to hide or show resolved or closed standalone issues.

This is because we're I'm not generally interested in them, and it could save a lot of space.

Make it so that hidden is default as well.

The Javascript is being loaded and run on all the project pages.
So on all Pages that are not IssueTab or ProjectPanelTab, JIRA throws an error saying that d is null.

Determining sizes for bigger data sets seems fine,
but for lower data sets, maybe make it a large portion of the screen size... by default (minus width of sidebar and height of header and legend)

On Issue page browse/ABC-123 Ajax refresh due to changing of workflow or commenting causes the Dependency Graph to disappear.

This can be fixed by setting an event handler on the Ajax page loader to call foresight_show.

When there are many loosely linked issues (more than 50 standalone issues when there are more than 100 total issues) the canvas size is too small.

Hi Travis,

what do you think about JIRA 7.x support ?
Any plans ? Need Support ?

Issue Tab Panel fetches all the items for the entire project along with links to items in other projects.
This is the same behavior as the project panel.

But why's this suddenly happening now?
Seen in JIRA 7.2.6

@joeeoj Hey Mike, in our JIRA at work, you managed to assign colors to issue types.... Is this the result of some add-on, if it's internal to JIRA, can you show me where the colors are set?

@joeeoj

Hey Mike, I'm thinking the ability to filter the project-level dependency graph by the Release/Version would prove invaluable to be a nice feature.

Do you think this may be worth looking into?