Drupal's core Forum module has a "Post new Forum topic" link at each forum, which can be used as an alternative to "Create content » Forum topic". It has the advantage that the forum the post should go to does not need to be selected from the drop down menu - the current forum is selected per default.

I wish the Support module implements this too - instead of Forum it's a Client here, but basically it's the same. My users often find the tickets list, but don't find how to create a new ticket. It would probably be more intuitive if they find it directly on the overview list of a certain ticket.

This would also solve the problem #377708: Make it possible to subscribe other users at ticket creation. because all the subscribable users are known from the current client on creating the node. the current situation where users can only be subscribed once a comment will be added is a real drawback.

Comments

jeremy’s picture

Assigned: Unassigned » jeremy
Status: Active » Fixed

Feature implemented:
http://drupal.org/cvs?commit=240112

Unfortunately it does not solve #377708 as there's nothing stopping a user with sufficient permission from changing the client at this point.

roball’s picture

Version: 6.x-1.1-rc1 » 6.x-1.x-dev

Thank you - just tried it in the 6.x-1.x-dev (2009-Jul-21) version and works fine.

If you wouldn't allow to change the client, but instead only offer the current client (on which list the link has been clicked from), #377708: Make it possible to subscribe other users at ticket creation. would be solved.

jeremy’s picture

I'd much rather see it fixed correctly -- adding kludges are a step backward in my opinion. Fixing #377708 correctly involves some AHAH / JavaScript talent, and shouldn't be especially difficult. Unfortunately it's not high on my personal list of priorities, but patches would be gladly accepted.

roball’s picture

Sure, fixing it "correctly" would be best, but until this is realized, the workaround mentioned above would be better than having nothing at all.

jeremy’s picture

Sorry, but I'm only interested in fixing this correctly, not working around it temporarily. The latter tends to mean that the former never happens.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.