#771 Provide a way (and document) to override default property values so plugin developers can do it - DataMapper

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#771 ✓not-applicable

Provide a way (and document) to override default property values so plugin developers can do it

Reported by Michael Klishin (antares) | January 15th, 2009 @ 05:46 AM

Comments and changes to this ticket

Michael Klishin (antares) January 15th, 2009 @ 05:46 AM
- State changed from “unconfirmed” to “confirmed”
Michael Klishin (antares) March 25th, 2009 @ 03:20 PM
I have a plugin for this already, need to move it to dm-more
Michael Klishin (antares) March 25th, 2009 @ 03:22 PM
- Milestone set to “0.10.0”
Dan Kubb (dkubb) July 22nd, 2009 @ 03:58 PM
- Milestone cleared.
Dan Kubb (dkubb) November 10th, 2009 @ 03:49 PM
- State changed from “confirmed” to “suggestion”
Dan Kubb (dkubb) November 10th, 2009 @ 03:49 PM
- Assigned user cleared.
Dan Kubb (dkubb) May 26th, 2010 @ 02:25 AM
- State changed from “suggestion” to “not-applicable”
I'm going to mark this as not-applicable, since I agree mostly with Sam's pov in the thread and don't think that some of the examples are clearer than the alternative.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.