Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Alternative Project View which shows all projects and branches #84

Open
dougthor42 opened this issue Jul 23, 2015 · 3 comments

Comments

@dougthor42
Copy link

First, let me say that I suggested this exact same thing to Travis-CI here, and I'm copying most of the post, really just changing an image or URLs.

I find that the user Project View (example) lacks information.

image

Specifically, a user cannot see all branches of all projects at once.

I propose adding an alternate view which fixes this. I've included a (very crude) mockup - a simple grid view where columns are various projects, and rows are their branches:

image

As you can see, all the same information is still there (Build #, Commit #, duration, end_time, status via color), but now we can see all branches. It would also be nice if the user could transpose the matrix, for those times when users have many more projects than they do branches.

Another example would be BuildBot's grid display, however this is only for one project at a time.

I was thinking of trying to do this myself within a standard webpage, but I've so far been unable to find any API that I could use to grab a user's (my) projects and branches.

I'll let your designers add all the bells and whistles (icons, proper font/color, etc.), but I think I'm getting my idea across.

Thanks,

@FeodorFitsner
Copy link
Member

Well, building dashboard around branches does makes sense, kind of "git-flow"-oriented design. Maybe this could be presented in a different way, like:

- Project 1
     branch-A
     branch-B
- Project 2
     branch-A
     branch-B
     branch-C
+ Project 3
+ Project 4

@dougthor42
Copy link
Author

That is definitely another good option. It removes the empty space that my design would have for projects that have few or no branches.

Personally, I'd like all project trees to be expanded by default, but I'm sure some other users wouldn't. Perhaps if it just remembered the most recent expand/collapse state?

@FeodorFitsner
Copy link
Member

Yeah, another consideration is performance as there is more information to retrieve and display on a screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants