#13: Related objects interface should be tighter (edit_inline)
-------------------------------------------+--------------------------------
Reporter: adrian | Owner: barbuza
Status: reopened | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday
nfa-changelist
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by anonymous):
Who do I need to talk to [http://www.guccishopping.com/ ed hardy]if I want
to help implement this?
That would be me. I go by "coderanger" on IRC, and can be found there most
of the time.
A (simple) ticket can be attached
to an (aggregate) ticket:
•to a milestone, as it is done now (display in the combobox only available
milestone tickets)
•to a master ticket (display in that combobox only available master
tickets)
It remains to be seen if an
(aggregate) ticket could itself be attached to another (aggregate)
ticket... A master ticket attached to a milestone makes sense.
You're quite right - reworking the modules and
breaking down the tickets into different types seems a good solution, and
more flexible than simply 'bolting on' master tickets.
Master tickets should be children of Milestone tickets, but not other
Master tickets.
--
Ticket URL: <http://code.djangoproject.com/ticket/13#comment:85>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
