Redmine

Request is too vague. What does "automatically" means?

Jean-Philippe Lang wrote:

Request is too vague. What does "automatically" means?

I think that should be configurable at the workflow

There is the category field which shall be used set to set an owner. (eg if you mean a guy who has to care for resolving the ticket)
Why shall status relate to an owner directly? That doesn't make any sense to me.

If you want a an owner to be set together with a defined status, the feature request shall look more like this.

"Set required ticket fields dependent onstatus", eg. you could define a status which makes the category (aka the "owner") required to be set or you can make a custom field "owner" (whatever that defines) set to required when someone set status to defined value.

That would nee the be able to set mandatory and optional fields for every tracker and every status, doesn' it?

Terence Mill wrote:

There is the category field which shall be used set to set an owner. (eg if you mean a guy who has to care for resolving the ticket)
Why shall status relate to an owner directly? That doesn't make any sense to me.

If you want a an owner to be set together with a defined status, the feature request shall look more like this.

"Set required ticket fields dependent onstatus", eg. you could define a status which makes the category (aka the "owner") required to be set or you can make a custom field "owner" (whatever that defines) set to required when someone set status to defined value.

That would nee the be able to set mandatory and optional fields for every tracker and every status, doesn' it?

In my company, after the ticket is resolved it will go to a test team.
What I wanted was to change when the status to "testing", it automatically changed the owner responsible for the tests.

Sorry about my english

+1

Think he means change the assignee as opposed to owner.

This is a fairly common itch to scratch, as larger groups and organizations have dedicated testing teams and issues/problems that are resolved should be assigned to a particular user, or a group of users when the status changes.

Other tracking systems seem to be implementing a function which can do items like change the assignee, send an e-mail notification, etc. after state changes.

I like the way the global workflows work, but I think items like this should be implemented/overridden on a project basis by role. Since currently assignment to groups (#2964) isn't possible yet you could assign a lead for each role for these types of state transitions.