If you need the granularity of being tied to a ticket, then just use that association to get all tasks under a category. Tieing them to both just make site complicated. Now, if you absolutely need to tie them to both, you should create an assignment table for that, which stores category_id, task_id.
Another assignment table for ticket_id, task_id. Then keep the task as one record, as supposed to duplicating data.
Actually dexter I had it commented out when I tried it and it's working now. So I guess what I came up with works just fine. Unless someone knows how I can refine it and make it cleaner.
It's working now.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.