Sign-in
About our forums

Our forum platform uses a separate login to identify you; it's not the same as your LiquidPlanner application login.

>> Login to the forums now 

If you wish to post and subscribe to change notifications, you will need to create a forum account.

After you login, you can access your profile by clicking your name floating at the top of the page. Clicking your name will also allow you to subscribe to e-mail change notification messages for the section you are currently looking at. 

Note, the forums are a public area. Do not post any private workspace content.

User Forum > Notification to the bug reporter

We recently started using LP for managing all of our projects. We also decided to go ahead and setup an dummy email address for Bugs section. Now, team members can submit bugs simply by emailing to that address. This is really great. The bug comes in as unassigned, and is assigned to the right person bu the project manager.

The challenge we have run into is, when the owner completes the task, the notification does not go out to the creator of that bug/task. So the person who submitted the bug has no clue when his request will be taken care of.

How can we solve this?

1) I know that if you "Watch" the task, then you get notified for any change. Can I add the "watch = yes" within the email itself. Because otherwise, having to go into the system and adding the task to your watch list kills the purpose of having an email to submit the bug.

2) Oh, and what about people outside of the team. when someone not oart of the LP instance submits a bug, is there a way to notify them?

This may be a new feature we just requested. Your help is greatly appreciated.

Thanks,
pd

August 13, 2010 | Registered Commenterpd

One way to approach this is to ensure that all bugs get submitted to a common folder or tasklist for bugs. Then you can watch the container, and you will be alerted to any changes on those tasks.

Perhaps we could allow people to automatically watch anything they create, I could submit that to the rest of the team as a new feature.

We don't have plans for emailing people who are not in the workspace about changes. If they are members of a project portal, they will receive updates about any shared tasks, which might work for you. Ig you have some intrepid developers, you might also look at using LiquidPlanner's API for your second case.

August 18, 2010 | Registered CommenterAdam