Is it possible to have multiple assignees to an issue.

I tried this - I chose to only change it for one project which meant I had to rename the Assignee field for that project to something else (I chose "Creative Assignee")  I'd like to be able to go back but looks like I can't at this point.  The other issue is now in the project settings, assignees tab, I get an error:

There is no "Assignee" field of type user in this project. It must have been deleted, renamed or detached

is it possible to fix this?

I see I can modify the new "Creative Assignees" by using the bundle...

One of the default workflows requires the 'Assignee' field, and is displaying that error. In the Workflow tab of you project, you can Detach the workflow causing the error, or disable the rule within the workflow.

Is there an answer to this question? I also want to have multiple assigned values to a single field (for example - I need the 'systems impacted' field to allow 1+ system values)

Hi there,

any time you can
- attach new field of type user[*], e.g. "Assignees", that allows set multiple assignees;
- convert existing field of type user[1] (e.g. "Assignee") to the multiple one of type user[*] (e.g. "Assignees")

Note, for any field type, except primitive ones, both single and multiple types are available.

YouTrack 4.1 types: user[1], user[*], build[1], build[*], state[1], ownedField[1], ownedField[*], group[1], group[*], version[*], version[1], enum[1], enum[*], integer, date, string, float, period.

We would like to assign these tasks to multiple people with the intention that these assignees divide up up task into smaller issues that will have a single assignee.

Returning to the first question the described behavior can be implemented by 2 project fields ("Single Assignee", "Assignees") and the workflow that will update parent task on subtask assigning/reassigning, something like this:

rule Cumulutive assignees 
 
when subtask of.isNotEmpty && Single Assignee.changed { 
  var parent = subtask of.first; 
  if (parent.Assignees.contains(Single Assignee.oldValue)) { 
    parent.Assignees.remove(Single Assignee.oldValue); 
  } 
  for each subtask in parent.parent for { 
    parent.Assignees.add(subtask.Single Assignee); 
  } 
}

Thanks, the user[*] helped me!

user[*]

Can anyone translate Dmitry's response into layman terms?  

I, too, am interested in being able to assign more than one assignee to an issue. I am using the in-cloud YouTrack. I am not clear from above response how one does it using the existing in-cloud UI.

Thanks.

Ignore my earlier comment. After a little bit more googling and finding another thread about this, I figured out where to go.

And by the way, this is VERY cool!

@Lisa I'm glad to hear that you studied out in field converting process.

Just for others those will read this tread: for converting single "Assignee" field to the multiple one you have to go to Administration > project > click on 'Assignee' field > optionally rename it and choose 'user[*]' as type.

You can also just attach new field of type user[*] on project screen: follow the wizard starting from link 'Attach Field' on the table header.