Assign ticket to a milestone?

I have developed a tracker module. I started using previously attached code, but I have rewritten most of code using code from ProjectMessages and ProjectTasks. Tickets are searchable, can have comments, subscriptions and notifications and attached files. They are included in project overview and I have added a tab to dashboard with tickets assigned to logged user. I think I have used projectpier coding standards. Attached patch is against 0.8.0 release

sergiocambra: Sorry, I spoke too soon. That error was my fault (PHP code caching was confused about the patches). However, I do get this error when trying to add a new project:

Query failed with message 'Unknown column 'can_manage_tickets' in 'field list''

Does the database need to be altered to use your patch?

Database must be modified if you have a install, there is a new column in project_users (a permission) and 4 new tables (project_categories, project_tickets, ticket_changes, ticket_subscriptions).

Instead associate a task item with a ticket, task items could be extended and converted in a ticket, or could be replaced with a ticket. Ticket has the same attributes as task items, and more (priority, type, category, description), plus comments and change history.

I haven't tried the new patch, but the way i read his response, I think he is going the other way around. Not task->issue but issue->task

Hey Sergio,

I think the patch needs more testing and review of things such as relating issues/tasks, plus we need to make sure it follows the coding standards. In principle though, I would like to include this feature in the next release. I would prefer to maintain somethign like this as module, but we won't have an API ready for the next release. Feel free to contact me directly, or discuss this further on the dev list. You can also get more support for your patch on the dev list.

just to say we have implemented the patch in our company (some files needed it manaully) but it works pretty well.

I was waiting to try it in my office. It's working here. Are notifications working for messages for example? Notifications are not sent to user which post the comment.

I could not get the patch in #1 working on Windows XP with Tortoise. Made manual changes to patch file (replaced diff's with Index row's and changed time labels to '(revision 0)'). Do not know much about patching so I'm not sure if done everything correctly. Anyway this modified patch works in my installations.

Do following:

1. Install fresh projectpier 0.8.0 release (with fresh database schema)
2. Run attached patch file on projectpier root directory
3. You should find 'My Tickets' link on Dashboard -page

Optionally to update existing service:

4. Create backup from your existing installation database (MySQL)
5. Restore database to new installation schema. Use differet table prefixes in order not to overwrite existing tables.
6. Remove duplicate empty tables
7. Rename tables so that old tables and new (tracker specific tables) have same prefix
8. Update the prefix to config\config.php -file as TABLE_PREFIX

The above works in my installation - no guarantee provided :) Thanks goes to sergiocambra for valuable effor - I think this is a very nice peace of functinality for Projectpier!

Oops... One more thing for the message #15:

While updating existing service, table 'project_users' needs to be modified: add new row 'can_manage_tickets tinyint(1) unsigned default 0.

Btw. The symbols for tickets and categories are not present on the patch - you need to create those for the theme you are using yourself...

Hi,

After applying the patch from knyar (great work btw!), we needed one more field to represent the 'state' of a ticket. Basically I added one dropdown, based on 'priority'. The different states we chose are 'opened','confirmed','not reproducable','test and confirm','fixed' and 'closed'. Changing this is merely a matter of changing the ENUM 'state' in PREFIX_project_tickets.

Because I don't know how to make a patchfile, I extracted the changed files. You can find them, together with the changes for the DB, in the attachment.

Note: MySQL 5 appears to have problems with updating an ENUM-field with an empty value. You can set sql-mode in my.ini to MYSQL40, you can add 1 empty value in the ENUM-field (add '' as a value), or you can prevent this from happening in the code. We went with adding ''.

Hope this helps someone.

I've tested your code and its great. Can I configure it in a way that tickets can be made with or without projects? It'll be a great help.

This is paramount to a good working Project Management software, and it works a treat! I would think though that a user should be able to see a list of tickets from the homescreen rather than just specific ones via a project?! I would have though that 'My Tickets' would show along side 'My Projects' and 'My Tasks'

Is there any reason why it doesn't??

Evening Gents.

Two words - awesome job. I finished up with merging all stuff and I'm surprised how nicely all system works.

I would like to ask you considering few things I have witnessed after using tickets for a while:

1. Sorting column in 'My tickets' view -> that'd be really useful.
2. Filtering columns wouldn't be bad idea as well - I think.
3. When editing the ticket and we're changing status from 'opened' to 'closed', would be good to make reflection when clicked 'Closed' on sidebar (currently system isn't indicating change).
4. Chart or indication of overall number of tickets / closed tickets and completion percentage progress bar - that's perfect solution in my imagination.

My initial budget for these changes would be £50 (I'm considering to increase of course) - I hope to resell some access to installation to my clients, more wishes would be more money.

Regards,

RRL