I really like how Trac manages my project but Drupal has many advantages such as permissions and management of multiple projects, but what would make Drupal perfect for project management is to add milestone versions and a view that shows percentage of bugs fixed to achieve milestone.

E.g.

 Miestone: 2.0 [***************60%         ] (60/100 bugs)
CommentFileSizeAuthor
#2 milestones-for-issues.jpg82.83 KBcliff_locus

Comments

joe-b’s picture

joe-b commented

+1 for this feature, definitely.

An interim for me has been to create a CCK type for milestones that can then be connected with issues by a node-relation. That doesn't give all the functionality by any shakes, but it does at least mean that particular issues can be connected to a milestone.

cliff_locus’s picture

cliff_locus commented
Version: 5.x-0.2-beta » 6.x-1.0-alpha4
StatusFileSize
new milestones-for-issues.jpg82.83 KB

bump. +1 for this feature.

I see a lot of potential for using this module in project management…
But milestone management is definitely needed if this is to compare with Trac or other robust tracking tools.
Here's my two cents on how milestone tracking should work:

  • create milestones for each project (sprint #, target date)
  • assign issues to specific milestones
  • filter and sort by milestone when viewing lists of issues (similar to how version is a filterable / sortable field when the Project Releases module is enabled)

See the attached image of how a milestone solution might look.

@joe-b: I tried your suggestion (CCK type for milestones) but things get ugly when there are multiple projects. Basically there isn't an elegant way to filter the display of milestones on a per-project basis…due to the inability to pass dynamic arguments when pulling a view into a node-reference field.

cliff_locus’s picture

cliff_locus commented
Version: 6.x-1.0-alpha4 » 6.x-1.x-dev
dww’s picture

dww
we/he/they
commented

On a project management site I'm building with project_issue, I just turned on project_release and created "releases" for various milestones. It's not ideal, but it definitely gets the job done for now. It'd be more complicated on a site that has both releases and milestones, but even then, it seems like using nodes to represent the milestones is still the right approach. Perhaps it'll all get cleaned up and beautifully generalized when we port all of this to D7 field API in the 7.x-2.* series and remove all the hard-coded custom content types...

Meanwhile, I encourage people to at least consider using project_release for this. You can pretty easily hide/alter all the stuff on the project nodes themselves about "releases" as such. See hook_project_page_link_alter() ...

boombatower’s picture

boombatower commented

sub from #1300972: Implement initiative content type

mitchell’s picture

mitchell commented
Version: 6.x-1.x-dev » 7.x-2.x-dev

*bump*

dww’s picture

dww
we/he/they
commented
Status: Active » Postponed

Yup, definitely planning to address this in 7.x, but not as part of the initial 7.x-2.0 release. We've got our hands full just getting the existing functionality ported to the core field API and killing all the custom content types. But hopefully it'll be quite easy to add this on once the underlying plumbing is in better shape. So, this might be a 7.x-2.1 sort of thing, not a whole new 7.x-3.x branch.

mgifford’s picture

mgifford
he/him
Primary language English
commented
Issue summary: View changes
Status: Postponed » Active

Checking in as we're at 7.x-2.0-unstable1 and this might be the time to address this in 7.x-2.x-dev

coming from https://drupal.org/node/1080550