It would be nice to be able to subscribe to a story and be notified when anyone adds a discussion note.
Watch story doesn't work on discussions.
by: Toni S. | over a year ago | Administration
Completed
Subscriptions to discussions
by: Toni S. | over a year ago | Administration
Copyright © 2025, Digital.ai Software, Inc. All Rights Reserved
Comments
Either a notification option, or a way to easily report or list recent discussions would be great. For example, "Yesterday's Discussion" or Recent Discussions would be nice.
We do like the feature in the mouseover popup that highlights the discussion bubble if there are entries. Perhaps that could be improved to highlight read if there are "new" discussion topics that you have not looked at.
We use discussions extensively, having QA and Dev distributed around the world, so improvements here are appeciated.
We would find both notifications & summary reports on discussions valuable. Our teams would like to use the discussion functionality, but without notification functionality, it does not meet their needs. Our Backlog Owners, BSAs, etc. would find reporting functionality useful to be able to identify areas requiring additional clarity (but this is less critical than the notifications).
I need to be notified if someone starts a discussion. Not just in response to my post, but a new discussion on a work item.
I use this so we can document the discussions, I use this for off shore work and they do not know a discussion. Now I have to save the e-mails and attach them. So I am not sure what discussions is for if there isn't any notifications.
Any news from VersionOne concerning this very helpful issue ?
We create code review "tasks" and update the story discussion with the review results. It would be great to be able to know if someone has created a discussion topic for code review results.
I would like to expand upon this idea by creating a user level setting that would automatically notify the user of any change to any object or child object for which that user is an owner, creator, or modifier. This would be similar to how Bugzilla notifies its users.
It would be good to see what discussions are happening automatically w/o havign to go back to it.
I agree that there needs to be a notification idea as Keith A. mentions above as well as the idea originally posted.
I echo Bryan W's comment above -- my team uses V1 with three different offshore vendors in four locations. Our offshore folks love the discussions attached to each backlog item/defect/request -- we were DROWNING in email before.
I really need to be alerted anytime a new discussion is started -- not just when someone replies to something I've posted. As a BA, knowing on which items my offshore developers need additional clarity is critical to a successful project.
It would be great to be able to subscribe to an RSS feed (or at least browse a list) of discussion updates -- something like....
UserABC commented on _BacklogItemA_
UserXYZ commented on _DefectB_
UserFGH commented on _DefectA_
UserMNO commented on _BacklogItemB_
...where the linked Backlog item or defect would take you directly to the discussion page for that backlog item, and anchor you to that user's comment with the panel expanded. Maybe in one of those really nice overlay preview panels that open when I click on the lit-up discussion/link/attachment icons.
This is a critical issue for us... currently, we do double/triple work and lose information. Because there is no notification specifically for a new discussion posting, we have discussions via email in our distributed development environment, and we have to remember to push those email chains into the V1 discussion tab to have the discussion recorded and associated with the V1 story. If discussion notification were enabled, we could better enforce the use of the discussion feature and save time by not having to duplicate efforts and would be more confident that our conversations are not being lost in the email vortex.
Discussions subscription is very much required, for us it's very painful track details through email and if team is adding any details in the discussions also we are not getting any notifications. this hepls a lot if the discussions enable through subscriptions.
Discussions subscription is very much required. This hepls a lot if the discussions enable through subscriptions.
Discussions subscriptions are useful and keep the concerned users updated without going into V1 for details.
Discussion subscriptions is very helpful and important communication chanel that can significantly reduce the information/discussion lost via emails.
It would be nice to have notifications when ever any team member add any points under the discussion tab. it will make team to be in sync with the current tasks.
We've used Bugzilla and JIRA in the past and one of the great things about both those solutions was how easy it was to have a discussion about the issue. Anyone interested in the issue receives email notification on every comment of the issue. For us, this is critical functionality that is missing in VersionOne.
We need to be able to subscribe to discussions as well as assign members to discussions. This is critial.
Yes, agreed with previous comment. We need to be able to subscribe to discussions as well as assign members to discussions. This is critial.
Would be nice to have an option to autosubscribe to any discussion where you've posted.
This is very much a half-complete feature; the Discussion lack of visibility makes it a black hole where communication starts but does not finish. I am considering disabling it as the current implementation hinders work instead of supporting it.
I'll throw my 2 cents in. I work for a large software company considering an enterprise roll-out of V1. Without fully supported discussion subscription capability, we'll have a hard time with adoption among engineers who are used to other tools with this functionality.
Another way users might manage subscriptions to discussions is to subscribe to any discussion where the feature or defect is part of XXXXX feature group. This way, product owners and team members can subscribe to relevant threads, as tagged by the team.
We started using VersionOne discussion threads but moved back to SharePoint when people started complaining that they couldn't get notifications. This is essential for our organization if we are going to use this feature.
Instead of having to watching all of my backlog items, my team would love to have a Notify on Discussion Updates for items that I am an Owner or Product Onwer on.
This would be a very helpful feature because there are many on our team who are unaware of the notes and questions that are posted to the Discussion section that could hold-up the progress of several backlog or other items in general.
We are using JIRA for our bugs and one of the great features of JIRA is comment updates. Similarly in Version One - it would be very helpful to have discussion updates to be notified.
Becoming the owner of a task or story should automatically add notifications for you. That way when someone adds a discussion thread to a task/story, the owner knows about it automatically.
Those associated with a story need a better way to communicate. The discussion field is great but everyone needs to know when any events are posted to the discussion board - not just when someone replies to their post. We have too much out of V1 email going on telling people about new board postings or people are communicating outside V1.
Much needed feature. Discussions without a subscription model seems like a bird with a clipped wing. There will be more user engagement when subscribers are notified of updates they are interested in..
Not only should subscribing to a story notify you of discussion posts, but its important that being a story or task owner automatically subscribes you to discussions that relate to it.
Notifications for recent discussion would be a helpful feature. It is better to know any events added to the discussion through notififcations so that we can be aware of it automatically instead of having watch all the items.
Much needed feature.
Discussions are pretty useless to us as there's no way for other team members to know when someone has posted one. Yes I understand that they go to the person they reply to or you can set up an email notification manually but why can't Discussions notification just be another alert like the ones that already exist. At this point, nobody on our teams is using Discussions due to this limitation. When can we expect some action on this item that appears to be a top request from the user communinity for some time? Thank you!
Much needed feature. Not having this hinders effective communication. Especially between QA and Developers.
We don't use Discussions because there is no way to know when someone created one! Please add this feature!
These are some enhancements that would make “Discussion” in V1 work better (and I believe would keep people from resorting to emailing important details and debates around):
• Owners + assignees = automatically watchers
• Ability to assign a watcher other than one’s self
• Update info captured in the body of email (so you don’t have to keep clicking a link to see what changed) – most important enhancement, if you are sometimes following on iphone as I often am
Communication is overall a big issue, lot of our product owners and developers have experience of working with BaseCamp and they found the discussions and automated emails sent from the V1 about discussion or notifications not useful. One proposal that came from our UXM team was to make discussions collaborative with emails, so everyone associated with the discussion automatically gets an email about anything new added to the discussion and when you reply the email (with the context of current discussion topic and the discussion chain), it automatically gets added to the V1 discussion log and is distributed to everyone else involved in the discussion on email. This allows collaboration via discussions, when you are not using V1 website. (discussions should also have file attachments, and you should be able to send the attachments via discussion emails too). e.g.
User A added a backlog Item/discussion, User B got a notification email. User B replied to the notification email with an attachment. (the content of the email reply automatically gets added to discussion, and an email is sent to User A with the details of what was added with the attachment.
Above example allows allows collaboration between everyone involved, and also saves the relevant conversations in V1 with attachments.
The Conversations functionality delivered in the Fall 2010 Release allows members to follow and track conversation activity within the system.
For more details, see the Release Notes:
http://community.versionone.com/Release%20Notes/ReleaseNotes2010Fall.aspx