as-ideas / ideas-dash Goto Github PK

As developer using the dash I want to be able to see which JIRA Bugs are currently in progress in order to be able to decide faster on which task I should work next.

And the class should support GZIP

travis should be configured accordingly

Configuration as file, persisted in database, via UI - whatever. Not in code any more.

Also we should improve the example app. Maybe there are some public jenkins-api or some open jira-portals we could use?

the backend should provide something like a deployment-id. if that changes the client should reload the page (to get new versions of resources)

Lets have users, teams, organizations via google login

we should include a module with an example-app to make development more configurable (currently ideas-dash has to be installed with maven and used in a consumer-dash to test changes).

maybe that example-app also could mock some services (jenkins aso) and be used for more automated tests...

maybe some people would want support for github pull requests on the dash (i think there is already support for stash?)

eg. dashing.io or https://github.com/40bits/teamwall

Maybe we should use teamwall as UI?

The UI should be:

• Clear, with bright colors (like it is now, and not like dashing with to much color and to dark)
• Empty if there is nothing to do.

• The PCP-Header is hardcoded in the restclient
• For many failing request eg. some VMs are not reachable the perfomance is under all pig

https://travis-ci.org/as-ideas/ideas-dash/builds/420852738 fails with the output

[ERROR] Failed to execute goal com.github.github:site-maven-plugin:0.12:site (default) on project dash-core: Error creating blob: Not Found (404) -> [Help 1]

I already upgraded to the latest version of github-site-plugin.

Is this maybe related to the cleanup of collaborators? Travis is using someone's credentials (i imagine the ones from @gaffa) and maybe he is not allowed to push to the repository anymore?

add a crashlytics-check that checks for app crashes in a given time period

as the title states

i guess there is a bug somewhere in the client code as my cooler began spinning real fast and the tab-task used 50% of my cpu (for comparison: facebook is at 5%). even battery went from 3h+ to 1h.

The current JavaScript code is a mess without any tests. Do something!

we should support icons on results

The pcp team has problems with updates from ideas-dash. Some commits have broken their monitor, as the changes were not compatible.

Could we have nightly builds and release versions?

Dashboard displays wrong time zone (UTC) without informing it.
In https://github.com/as-ideas/ideas-dash/blob/master/dash-core/src/main/java/de/axelspringer/ideas/tools/dash/presentation/UiInfoService.java#L56 I would suggest to use ZonedDateTime() with format pattern that can be read by Angular (here I can't help, since I don't know Angular at all)

We have very fragmented and dirty filtering mechanisms in the different adapters. This needs cleaning up.

the settings (aggregate/team) should be saved in browser.

it should be possible to map a checkresult to multiple teams if they share a codebase or other responsibilities. we would need it for at least jenkins and datadog.

the dash readme is really not comfortable enough

the javascript-file has a frightening tendency to do too much. rip it apart :D

we at upday would like to have only alerts with a specific tag displayed red on the dash. all others should be yellow. therefore we should externalize the configuration (like in the jira-case issue-51)

Hi @Waschnick,

what are your plans with this project? You recently removed @gaffa and me from the collaborators. We understand that since we are no longer part of as-ideas, but how can we continue on developing it with joint forces? Or are you planing to abandon it completely?

We are still actively using it and want to continue adding more features and improving it.

we would like to have a special logic for the visualization of bugs on the dash for upday.

• bugs older than 5 days shall be red
• bugs that are blockers shall be red
• all other bugs shall be yellow

as this may be project-specific we should implement it generic/configurable

currently the group order seems to be hard-coded for the originating project (pcp). it should be configurable so it can be used by other consumers as well.