Closed (outdated)
Project:
Support Ticketing System
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Oct 2011 at 17:15 UTC
Updated:
29 Mar 2023 at 19:53 UTC
Jump to comment: Most recent
Comments
Comment #1
LinuxETC commentedLooks like the "double entry" could be from the Project ID starting at "2" instead of "1" like I would expect in the databases.
I also noticed there are now two Project tabs formed with the Project title with the Client overview (this Project was assigned to a specific Client for reference).
Comment #2
bdragon commentedLooks like the primary cause of this is blindly assuming the node body field is not empty.
Since drupal tends to not set up the field structure when that field is empty, I need to add some additional checks.
Comment #3
bdragon commentedFixed, thanks.
I also fixed rendering to use the correct filter instead of always using the fallback filter.
http://drupalcode.org/project/support.git/commit/186322d40208df7572211c3...
Comment #4
LinuxETC commentedLooks like there is still the duplicate project tabs when going to the Support Overview of the client with the assigned Project.
Thoughts here?
Comment #5
bdragon commentedAre you sure you don't have two projects?
What are the paths the tabs are pointing to?
Comment #6
LinuxETC commentedIt is one project. There is a slight path difference noted below:
(site URL)/support/(client)/active/(project name)
(site URL)/support/(client)/new/(project name)
Which I see is related to if the ticket State = "new" or "something else" where it will show up in the proper Project Overview page.
So this is not an issue, just needed some clarification it seems. I believe Jeremy is working on some documentation with respects to the Support Project module, so perhaps this will be included.
Thanks for the assistance!
Comment #7
bdragon commentedThere should be a set for each state. The projects are subtabs of each ticket state. Are you doing something special with theming? In the seven theme the subtabs show up in a second row under the state tabs.
I know that this is suboptimal, and I'd like to redo it , but have been focusing on more critical issues.
What do you mean by "project overview page" by the way?
Oh, and if you have any ideas for a better scheme for laying things out, I'd love to hear them.
Comment #8
bdragon commentedOh, also, note that the tabs are being used as *filters* for the ticket queue. Additionally, projects are actually optional. If we wanted to have a project tab selected at all times, we'd need to add a "No project" one, I suppose.
Comment #9
bdragon commentedWell, I guess they aren't optional once you've created them (which I guess may be a bug), but tickets created before you made any projects won't have one, so won't show up in the queue if you have a project tab selected.
Jeremy?
Comment #10
jeremy commented> tickets created before you made any projects won't have one, so won't
> show up in the queue if you have a project tab selected
Correct. This is the behavior in 7.x too.
In the 7.x-2.x branch we will be refactoring this; ticket listings will be built with Views and proper filters.
Comment #11
LinuxETC commentedThanks. The following is a feature request that addresses similar to what Jeremy noted
http://drupal.org/node/1302766
I can wait for 7.x-2.x hopefully. ;-)
Comment #12
purencool commented