Make it possible to subscribe other users at ticket creation.
greta_drupal - February 20, 2009 - 03:14
| Project: | Support Ticketing System |
| Version: | 6.x-1.0-rc1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Would be nice to have the "Subscribed" section on the initial job ticket form as well -- not just on the comment form. So that notification recipients can be assigned on initial job ticket entry.
As it is now, I'm not sure who is getting the initial ticket notice. Anyone other than admin? (The email notifications are not working for me, and I couldn't determine that by looking at the module code.)
#1
This will require some Ajax integration, as the list will need to be updated if the client changes. Marking postponed until someone contributes a patch.
#2
Updating title to match this related issue:
#436726: Make it possible to assign ticket to other user at ticket creation
#3
Moving to the support module.
#4
The notification module provides all of these features... I wonder why this is not implemented?
#5
Perhaps because you've not yet contributed the necessary patch?
#6
Perhaps its because this issue has already been brought up, and that the suggestion for including notifications was shot down. Perhaps I bring it up again because scope creep has now made my initial suggestion valid.
When I made the initial suggestion I was willing to work on this project. The response I received not only prevented me from contributing on this issue, but multiple hostile responses to such suggestions has basically set up a situation where I will never contribute to core.
Certain individuals discourage contributions. Then they voice concern over the issue that no one wants to contribute. The response that no patch was made only heightens the problem. Why would I spend days and weeks on a feature if certain people control the gateway to the inclusions of such features. Without their approval the contribution will not be included. Thus it would be wise to ask if your work would be included before you spend the time writing such projects.
In this case I asked a valid question. Which is why we do not use the notification module? A response of "Thats a good idea" would possibly get me to work on it. The response you gave is essentially a response telling me where to put it. Thus this hostile response leads me to my initial opinion that contributing to Drupal's core or website leads to drama and no solutions.
Thanks, but no Thank you.
#7
Ohh and sorry that I spent some time on the issue queue. Its clear now where that gets me!
#8
Good luck with that.
For what it's worth, you may be a little confused: this is not a core module, and I have no idea what previous feedback you're referring to that has upset you so. As for the notifications API, it's a massive framework and not something I'm especially interested in making this module dependent upon. As for my response in #5, I was offering an ironical response to your question "I wonder why this is not implemented?" You nor I have submitted a patch, so it remains unfixed.
#9
Feature committed. I did not use AHAH, so if you change the client the list of users to subscribe does not change.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.