Let me refine the situation:
[model A] -> foreign key on [model B] -> foreign key on [model C]
When I create [Model A], it may only refer to any [model B]
that is attached to a specific [model C].
If I get it right, I should create a custom AddManipulator,
with a [model C] as its parameter. A
On Thu, May 04, 2006 at 10:32:59PM +0200, Moi Meme wrote:
> And on my particular ticket system case, Paul Bissex's 20 mn trouble
> ticket system (http://e-scribe.com/news/230) looks cool, but is limited
> to one model, which takes its list of applications from a static list
> (INSTALLED_APPS).
I had the same idea at first: Application -> Milestone -> Ticket (using
a generic milestone for tickets not assigned to any specific milestone).
But indeed, it does not fix the problem, when tickets need be created
against a restricted list of milestones linked to application A.
The admin
For a some ideas, you might want to have a look at Paul Bissex's twenty
minute trouble ticket system: http://e-scribe.com/news/230
John
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post
Hmm, after rereading my reply, I seem to just be restating your
problem to you without explicitly stating my answer. I was trying to
suggest that you alter your model by removing the 'application'
ForeignKey from 'Ticket' as it is unnessecary.
Obviously, in the admin, you would want to give a
>
> class Ticket(models.Model):
> """ Tickets are created on an application and may be attached to a
> milestone (optional). """
> name = models.CharField(...)
> application = models.ForeignKey(Application)
> milestone = models.ForeignKey(milestone, blank=True, null=True)
>
You
Hi,
As a pretty new user, I have been through the tutorials and experienced
a bit, playing with magic-removal branch before the merge.
(Note to the impatient: my question is at the end of the mail)
I'd like to build a light ticket management system for my work team, and
came up with the
7 matches
Mail list logo
