We've recently been trying out conversations and believe they have become much more useful with the email notification feature. We have found them a bit clunky for a couple of reasons, though. One reason is that the Subject of email notifications are all basically the same. You have to view the email to know what it's in reference to.

A useful addition would be the ability to control the Subject of the email that is generated by the conversation. Right now, they all come in as "<name> mentioned you in a VersionOne conversation." or something similarly generic. Some ideas:
- VersionOne could make a best guess on what to put in the subject (the backlog item ID, comma-concatenated list of items mentioned)
- Add a field in the conversation that allows the user to enter a subject
- Add a field in the conversation and default it to a VersionOne best guess that the user could change
- Allow the user to select one of the items mentioned (via radio button or something perhaps) in the conversation to be placed in the Subject

Thank you!
- Mark

Comments

  • This makes perfect sense.

  • I would be happy to see the Story ID - Title in the subject of the email so they could be easily sorted and identified.

  • Same for me - i would like to see at least the name of item (task/story/ etc) for which this conversation was started in the subject.
    This would make it much easier to see which topic was discussed without clicking on the reply button

  • The conversations sends email, but the subject is not very informative.
    As we have different roles, and sometimes you are linked in just for information, in other cases you need to make a deciscion for the item. Is it possible to wrap the subject field to provide more information, e.g. the subject field below could be:
    “D-01506: Error when export file to accounting system, comment from <User>”

  • Hi, regarding emails generated by the conversation feature:
    - They should include content that is relative to the context of where the conversation was started. For example, if the conversation is for a task, include the project, epic, story, and task fields. It would be great if we could simply check of fields that we want included (regardless of the context and whether the field has a value).
    - Regardless of what's included in the email, the entire conversation thread should be displayed, ideally in a descending sort so that we see the latest message first.

  • As several people have already mentioned, at least please make the mentioned Item used as the Subject of the email. This is a very old request now; what's the ETA for some type of improvement?

  • It seems that VersionOne is not listening to their customers at all and ignores this. The current way subjects are created is total nonsense anyway and indicates that no-one really put some thought in it. Most email clients group the same subject emails together, but now all comments from a single person is grouped together, rather that comments from one defect or backlog item. The subject should therefore contain the defect number of backlog item number with the short description of the case and be the same for the whole conversation (otherwise email grouping is not working correctly).

    Please listen to your customers as the email feature is a big nuisance now.

  • I agree. The conversations emails don`t have references to the conversation and V1 ticket unless they are specifically mentioned in every reply in the conversation. That does not make any sense... Please implement what Mark has suggested!

  • Indeed! I agree completely. As a work around I copy/paste the defect or story title and # into every conversation reply I send. Unfortunately not everyone subscribes to this & I end up with a slew of unintelligible emails from noreply@hosted.versionone.com with no reference to item.

    Since most people work through email, having to go back into V1 each time to look up what a conversation is about is tremendously inefficient. Perhaps if I only ever received a conversation thread about a single issue at a time this might make sense, but not when you are getting bombarded on a daily basis about multiple items.

    Please listen to the posts on this issue. Thank you.

  • I definately agree with the idea but would like to know what is being changed/added in the planned release of VersionOne application based on the idea

  • Thanks for your input. The conversation notification subjects now provide more context about the mentioned asset. This was delivered in the 14.1.3.49 point release. https://community.versionone.com/Release-Notes-and-Downloads/Spring_2014_Release_Notes/Spring_2014_Point_Release_%233_-_Build_14.1.3.49