Haven't fully explored it yet, because I am not an admin yet on
redmine, but it seems to me that the Target Version feature might be
what we need.
On Oct 21, 10:37 am, s...@monkeytownhq.com wrote:
hi all -
At the meeting with the developer team last night there was an
important discussion of how to leverage software like redmine to
establish a reliable project management workflow.
To everyone who has worked to set up the redmine issue tracker,
thanks! This is a critical tool for turning team input in to
From what I am able to see in the current implementation, there are
two levels in redmine: projects and issues. Issues within a project
are in a single list, but can be tagged to be filterable.
A key need expressed at the meeting last night is to group tasks in to
time boxes - what's being rolled out this week, next, the week after.
It may be possible to employ redmine to indicate time boxes, but I
don't see this immediately facilitated in the current interface.
I have attached two screenshots of the tool I use to accomplish this
in my work, active collab.
activecolab-tickets shows the ticket list chunked into timeboxes with
title headers, and at-a-glance summaries for each ticket (most
importantly, who is working on it). As a manager, as deadlines
approach, I can triage by dragging tickets that won't be ready from
one time box to another.
activecolab-ticketdetail shows the detail screen for each ticket. The
important thing here is that there is a discussion thread interface
for each ticket, so you can have long discussions for each issue with
just the team working on that issue without cluttering up the
project-level discussion board. You can also post assets needed for
each ticket on the ticket itself.
I'm not posting this to argue for one tool over another. This is a
recommendation of features that I feel will address the communication
needs raised by the developer team. If this can be achieved or
approached within redmine that would be fantastic.