Project

General

Profile

Actions
Copy link

Feature #2481

open

Improved issue update (+post real-life project information).

Added by Jens Berlips over 15 years ago. Updated over 14 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2009-01-09
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Hello, Thanks for an excellent project management system.

We have worked with Redmine for a 2 month project now, and it ended a few days ago. I wanted to share some ups and downs and also make a suggestion which I feel could add some real value:

We developed 5 applications, 3 mobile apps and 2 client apps.

How we worked:

  • No emails between providers/workers. Only updates within Redmine.
  • One project, versions were actually used (faulty) as subprojects (which worked though..).
  • Decentralized organization (spread over the world (Sweden, Ukraine, India etc.).
Ups:
  • Excellent user interface.
  • Easy to understand (even for non-specialists).
  • Very easy to update
  • Manage plenty of projects is more or less a dealbreaker compared to Trac.
  • Excellent admin system.
Downs:
  • Grouping of issues is much nicer in Trac, and this is really valuable. For example Trac version This has no real currently comparison in Redmine
  • If you use a project with many subprojects, you cannot really have a good overview, in terms of how versions are represented with bars etc.
  • Issues really get bloated in our way of working, it become more of a chat room (SEE BELOW).
  • Would be really good to have group permissions on issue level.
  • In general, the better we could visualize issues (to get an overview) and their progress the better.

PROPOSAL:

  • Currently the update is just a linear list of updates, in one category.
  • It would be really good if we could separate this in two parts (or perhaps more?).
    • one part keeping the current , where the updates are more to make actual updates of the issue (time-log, concrete updates etc).
    • another part could be a discussion forum (similar to "forum") where you discuss the issue and how you could deliver it. Driving work and delivery forward.

This will make the issue update process much easier to follow. And the forum could potentially be used for building a best-practice database (Knowledge base, FAQ and similar).

What do you guys think about this?

Thanks again!

Best regards,
Jens Berlips

Actions
Copy link

Also available in: Atom PDF