It's generally best practice to have a single person accountable for the issue so that there is no confusion in expectations-setting and delivery.
If you have jira-admin permissions, you might consider adding an additional multi-user picker custom field to the screen assigned to the issue type that might be called "Additional Responsible Members."
Another, likely better, solution might be to assign a higher level issue, usually called a story, to the accountable team member, and then break it down into tasks, assigned to other responsible members of the team.
Thank you Beth Schaefermann. Administrator rights are. The fact is that now that the task assigned to multiple assignee it just creates a few times with different assignee.Now they want this process to reduce to a minimum. Ready to when creating a new task to specify multiple assignees and set up different tasks for each of the selectedassignee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There may be a lot lost in translation. www.translate.google.com is one of the better tools for helping. It sounds like you might want to be creating stories and tasks using a template, something I am also looking to do. Right now, the only solution I can tell is cloning a story, which creates the story and tasks anew with the same assignees. Documentation on cloning: http://confluence.atlassian.com/display/JIRA/Cloning+an+Issue
I don't think my response directly addresses your need, but the translation is difficult. I'm sorry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.