The need for structured communication heightens when clients and developers do not work in the same location. Lack of a standard system is prone will result in a chaos caused by a pile of emails intertwined with various phone conversations no one seems to recall in quite the same way...
The developer is stuck and needs instruction from the client. The initiator should respond to issues and change the status to "open" so work can continue.
The initiator has the final say in what is acceptable and therefore has the privilege of closing the issue. The ball is in the initiator's court to either close the issue or make a comment and reopen the issue.
The developer is in charge of getting this issue done. When the issue is fixed, the developer makes a note and sets the status to "fixed waiting approval". If the developer gets stuck, the developer makes a note and sets the status to "needs clarification".
Message: The edit comment page doesn't work right.
Comment: Please give a step-by-step outline describing what you are experiencing.
Status: Need Clarification
Comment: I logged in as myself. I was on http://arsdigita.com/vision . I clicked on edit under my first comment. I changed the title from "I LUV this vision" to "I love this vision" and pressed Submit. When I looked at the page with all the comments, the change was not there.
Comment: I've edited /general-comments/edit-comment-2 to update the comment title in the database. You should now be able to run your example successfully.
Status: Fixed waiting approval
Comment: Oh yeah, instead of saying "Submit", I'd like the button on http://my-service.com/comments/edit-comment to say "Edit Comment".
Comment: I've edited /general-comments/edit-comment so that the button says "Edit Comment" instead of "Submit"
Status: Fixed Waiting Approval
From time to time, the process will go astray. You will get a solitary email with some tasks. This is the time to reinforce proper use of the system.
You'll come to develop a style of your own to do this, but here are a few templates to get you started.
Is there any reason we are not using the on-line collaboration system that we have been perfecting since 1994? "The Book" (Philip and Alex's Guide to Web Publishing) will give you an idea of how ArsDigita operates in just 17 chapters. Philip up late cranking out my next book
Please put this in the ticket tracker. Thank you, Tracy
Thank you for writing. I am confirming that I have received your email and I will investigate how to fix this issue. I am sorry I haven't executed what you need and will try my best to rectify the situation. Perhaps I can suggest that we use the ticket tracking system that is set up your staff server. I was thinking that this would allow you to see and comment on any questions or concerns you have about this issue at any time. I've added this issue to the system for you and made sure it appears as your entry. This will ensure you get automatic email responses of any notes that are made. Just to be sure we are on the page, here is exactly what I did:
Please take a look when you have a moment, and let me know if you think the user interface is sufficiently clear. Any suggestions on how to improve it are, of course, welcome. Hope this helps, Michael
- Going to http://your-servicename.com
- Logged in
- Clicked "ticket tracker administration" from the workspace
- Clicking "add and issue"
- Filled out the form with your instructions and hit submit
"I live in the ticket tracker." Atiasaya - GuideStar
"I LOVE the ticket tracker." Sheila - Infirmation (personally posted 350 tickets in a 2 week period)