Personal tools
You are here: Home Products Poi Roadmap #2: Issue deadlines
Navigation
Log in


Forgot your password?
New user?
 
Document Actions

#2: Issue deadlines

Contents
  1. Motivation
  2. Proposal
by Lukas Zdych last modified June 11, 2006 - 00:22
Add the ability to define and track deadlines for issues
Proposed by
Lukas Zdych
Proposal type
User interface, Architecture
Assigned to release
State
rejected

Motivation

In cases where it is important to define issue deadlines and finish issues before such a date, there it would be useful to alert users with issues close to it's deadline or in bad cases after it's deadline.

Proposal

  • Add deadline:DateTime to issue schema
    • it is very important info for some kinds of tracking
    • should be available only with "watch deadlines" turned on in the tracker
  • Add watch_deadlines:boolean to tracker schema
    • should be used for watching issues which are close to dead-line and those which are behind deadline
    • alert issue tracker manager and responsible users about those issues by displaying them in highlited area on title page of tracker

note: proposal still in progress..

Releases

Posted by Martin Aspeli at December 21, 2005 - 00:57
In the PloneSoftwareCenter scenario, the target release (see proposal 9) acts as an effective deadline for all issues assigned to that release. I'm unsure whether it's necessary to have both.

You're right if Poi is in use with PSC but..

Posted by Lukas Zdych at December 21, 2005 - 08:36

The signal for makin this proposal was to support more an help-desk scenerio where it's not about just software development but also single tasks and so on where your are not using Poi in combination with PSC for example.

Focus

Posted by Martin Aspeli at December 22, 2005 - 22:07
Yes. The question is where we're headed. I'm actually not very keen on putting this use case into Poi core. Poi is a software tracker first and foremost. It's not a generic ticketing system, it's not a help desk system.

I want to make Poi much more extensible for version 2.0, and here such use cases can be supported. But the more I think about it, allowing "just one more" feature out of the core use case will mean that Poi becomes PloneCollectorNG2 - powerful and heavy.

Ok.. I agree

Posted by Lukas Zdych at December 22, 2005 - 22:13

So assign this proposal to version 2.0 or simply reject it ;)

Refactored

Posted by Martin Aspeli at December 23, 2005 - 12:57
This is being moved into proposal #8.

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by