Ticket/Project Communication

Another TDX philosophy question...

For tickets,

  • How does TeamDynamix recommend letting regular people know of changes to the ticket?
  • How does TeamDynamix recommend letting insider/technical people communicate with each other so that their communication doesn't obfuscate the former communication?

For projects, same questions:

  • How does TeamDynamix recommend letting regular people know of changes to the project?
  • How does TeamDynamix recommend letting insider/technical people communicate with each other so that their communication doesn't obfuscate the former communication?

I can tell you how we do these, but it might not be the recommended way.

Tags notification ticket-update comment project-update announcement
Asked by Greg Van De Mark on Tue 7/23/19 4:31 PM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Mark Sayers Wed 7/24/19 9:22 AM

Hi Greg,

I think for each item (ticket and project) it might be helpful for us to know what your definition "regular people" would be since it sounds like that could make a difference in the recommendation that we might give for handling the given scenarios.

Also what sorts of changes might you be letting them know about? Just closures, an update on where the ticket request is at currently in its process of being fulfilled, or what?

Sincerely,
Mark Sayers
TD Support

No feedback
Sorry for the broad initial question. I seem to do that when asking my "philosophy" questions. Search your questions area for "philosophy" and you'll see.

We are making a concerted effort for people to enter their simpler, low risk projects into TDX for visibility (to managers and campus). Periodic project updates will be part of the deal. In talking about how these people would update their projects, I proposed that they would update management/campus using "(project) > Manage > Update". (The same principle applies to ticketing.) A question came up on how a person would communicate more technical information or items that they would like to keep in the family. I suggested going to the feed and commenting (and optionally notifying). (Again, the same principle applies to ticketing).

(Stay tuned for part 2. This comment box is limiting my response.)
- Greg Van De Mark Wed 7/24/19 10:49 AM
(This is part 2 - just in case the comment order is not what I expect.)

Another person asked about Announcements for internal communication. I have never used that functionality. That might be the answer but it isn't available in ticketing and I don't necessarily want to have a different rule when updating externally/internally between projects and tickets. I try to keep things as similar as possible. That is why I'm asking the question.
- Greg Van De Mark Wed 7/24/19 10:49 AM
Would a call be easier? I am free now. Is the phone number ending **87 still the best one for you, or do you want to just call our number? - Mark Sayers Wed 7/24/19 11:06 AM