When creating a bug need a default Assigned to... user

[mariusmotoc]

Hello!

I'm kinda new in using Sugar... so please help me.

I noticed that when I create a bug from my account in the field Assigned to by default it's written my account.

My question is:

Is there any possibility that by default a different user name's account can be put there?

I'll tell you why I need this.

I want that some users (that will only create bugs to notify the helpdesk manager) to assign the bugs to the helpdesk manager, so by default it will be easier for them that the account of the helpdesk manager will be by default in assigned to field at bug create. I don't mind if the helpdesk manager's acount will be the default user account selected in every module at creating any new task in modules.

Thank you for your time!

Marius

using
SugarCRM
Version 5.0.0b (Build 3150)

[Angel]

Is there any possibility that by default a different user name's account can be put there?

I've had similar needs in the past. Unfortunately, there is no way to do it via built-in features.

You might be able to work around it by using logic hooks to invoke some custom code when the record is being edited, but this may not be an ideal approach as it doesn't handle new records well.

What I've had to do in the past is modify the Sugar code to get it to default.

So, in short, it is possible, but it will require a code change or you'll need to live with some limitations of the workflow if you want to do it via a logic hook. The advantage of the latter is that it is upgrade safe, while a manual code change isn't.

[mariusmotoc]

I've had similar needs in the past. Unfortunately, there is no way to do it via built-in features.

You might be able to work around it by using logic hooks to invoke some custom code when the record is being edited, but this may not be an ideal approach as it doesn't handle new records well.

What I've had to do in the past is modify the Sugar code to get it to default.

So, in short, it is possible, but it will require a code change or you'll need to live with some limitations of the workflow if you want to do it via a logic hook. The advantage of the latter is that it is upgrade safe, while a manual code change isn't.

thank you for this hints.