Redmine - design study
I'm trying to give some ideas for the redmine interface. Currentyl I'm trying to define some screenshots. It would be great to have some feedback to this suggestions.
In the coming days, I'll upload some other suggestions.
#3 Updated by Jan Niggemann (redmine.org team member) about 7 years ago
- File project_overview.png added
Additional_ProjectOverview_01.png better than
..._02.png because having tabs requires additional clicks from users...
That said, the "subproject" section could / should IMHO be made a list and ordered by name (see project_overview.png)
#4 Updated by Daniel Felix about 7 years ago
Jan Niggemann wrote:
..._02.pngbecause having tabs requires additional clicks from users...
You're right, but on the other hand, you'll have to generate each list even if the user doesn't click on it. The grouped elements would give the advantage of ajax requests.
#5 Updated by Filou Centrinov about 7 years ago
Project Overview: Yes, ticket box to the right is nice, because i don't use news (box). ...but may be not everybody is happy about this :-)
History Overview: Make it possible to set a default. Make it possible to show and hide tabs. Also "spent time" tab would be nice. May also optionally conclude multiple actions like 5 times changed description from same person and no other activities had occured in that time.
#6 Updated by Terence Mill about 7 years ago
If a info box is showed, how is layout and orientation shall be configurable.
For example see plugin redmine_blocks_layout which offers such feature.
Additionally there shall vbe plugin whoch extend for new info boxes, like redmine_polls and redmine_last_messages
A newplugin that shall be integrated to support box layout is last issues
#8 Updated by Anonymous about 7 years ago
In terms of design, I think there's a really simple approach that could be taken here. In terms of implementation...ehehhe...haha...well, anyway. Let me break it down--I'll be referring to the elements on the overview page as 'blocks' for this post:
- Overviews need to allow for customization, in the same way My Page is customized. The blocks that exist now become a standard set of modules that can be added or removed as people like, or reset to a default layout.
- Introduce two 'custom' blocks: Query and Wiki, and users can add as many of these as they like.
- Query Any existing saved query for issues can be selected here, and the top x number of posts from the query results are displayed. It's just as interactive (right click) as the My Page issue lists.
- Wiki Any existing wiki page can be selected here. This allows for project introductions that don't pollute the /projects page view (you know what I'm talking about), as well as the addition of graphic content. I personally maintain wiki pages with status charts, and I'd love to have a block for these on the overview page, ala dashboards.
- Enable all of the same customizations on the Home page, for a global content view. Wiki blocks might be more complicated here, though, unless you allow for the identifier:wikipage syntax when choosing.
This leaves us at one last detail: ditch the My Page feature. Once the overview model is expanded to allow for customizations, My Page becomes redundant next to Home. Its calendar module is unique to it right now, but even that could be turned into an Overview module (it could use some design love, too).
There are some questions to be answered, of course. How many levels of customization are there? Is there a global module default, similar to all the other global defaults (modules, columns)? Is there then a project default, where manager rights allow you to set the official project overview layout and content? Is there then still one more default, for each user, who wants to add the content that matters most to them? Prioritization is clear (user default overrides project default overrides global default), but would we want all three levels? Would there be, for users, a "Reset layout" link that would purge their changes in favor of the project default? Can they save views as templates to toggle between or apply to other projects? Lots of questions!
Regardless of the details, I do feel strongly about movable blocks and the addition of wiki and query blocks. Those two changes alone would dramatically improve the Overview's usability and appeal.
I do like the grouped tab concept, but I don't think it should be limited to a static set of block types. You know how you can drag a tab from one browser window to another browser window? Do that here! As you're moving blocks around, if you hold the block over another block, they join and become separate tabs of the same block space. Add more blocks here, creating more and more tabs (some interesting things could be done with this and wiki blocks). Grab a tab and drag it away and it separates into its own independent block again.
#10 Updated by Dipan Mehta about 7 years ago
In my opinion, there should be a straight forward policy for a clean design -
_More static content on the left [Including summary, member lists, etc.] and dynamic content on the right.
As far as dynamic content is concerned, I think following might be interesting
- Issue tracking box.
- A box containing the progress bar of currently active versions
- A box that show's two days (or a few days of activity)
- News etc.
Typically, these can be either tabs, or better still it can be a collapsible block if there are too many blocks involved.
The extra content such as "Participate in the latest polls", "Hall mark Developer of the month" (or link to it) should be on the side bar. Typically this shouldn't be a widget - rather a plain wiki or HTML page which can be decorated and edited as the Project Manager wants to put it.
#13 Updated by Dipan Mehta about 7 years ago
I am not sure this is a right place to put this comment but I want you to highlight on specific UI related issues:
- take a look at #3930 in dealing with long/large lists. It would be good if we have auto complete type fields for the same.
- take a look at #3543 in dealing with long-text type fields. Looks like 1 column layout in issue page and update form would be more optimum if there are long-text fields.
- as per #4967, Issue colors and it's theme support
- Related to roadmap page - #1936, #13548, #4291, #7270
- Roadmap on My page #10979
May be you want to add all this as related.