Project

General

Profile

Actions
Copy link

Defect #13764

closed

Unable to create a new ticket from an email

Added by chris p over 11 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Email receiving
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:
2.3.0

Description

I get the following error when I try and create a new ticket from an email, can any one help? This is a new enviroment and is the latest version

Validation failed: Assignee can't be blank

I have searched high and low but am unable to find a solution. I can update existing tickets as the assignee is set for them.

This is my env:

About your application's environment
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.8.15
Rack version 1.4
Rails version 3.2.13
Active Record version 3.2.13
Action Pack version 3.2.13
Active Resource version 3.2.13
Action Mailer version 3.2.13
Active Support version 3.2.13
Middleware Rack::Cache, ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x7ffa5693c738>, Rack::Runtime, Rack::MethodOverride, ActionDispatch::RequestId, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::DebugExceptions, ActionDispatch::RemoteIp, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::Head, Rack::ConditionalGet, Rack::ETag, ActionDispatch::BestStandardsSupport, OpenIdAuthentication
Application root /usr/share/redmine-2.3
Environment production
Database adapter mysql
Database schema version 20130217094251

Environment:
Redmine version 2.3.0.stable.11679
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.13
Environment production
Database adapter MySQL
Redmine plugins:
ekanban 0.0.1
redmine_default_assign 0.2.0

Thanks in advance...

Actions
Copy link
 #1

Updated by Daniel Felix over 11 years ago

Do you have changed the assigne field as required in your workflow?

Best regards,
Daniel

Actions
Copy link
 #2

Updated by chris p over 11 years ago

Hi Daniel, thank you for the response, I am still a bit confused and my new ticket via an email is not working these are my workflow settings:

Manager    Developer    Reporter    Non member    Anonymous
Bug    31    14    6    1    1
Enhancement    31    14    6    1    1
Feature    31    14    6    1    1
Support    31    14    6    1    1

I have just set all the User Groups to be able to add issues and so they all have the new status checked?

cheers chris

Actions
Copy link
 #3

Updated by chris p over 11 years ago

Hi, could anyone help me with this I am really excited to get this working for our company but without this main functionality we just cannot use it.

Actions
Copy link
 #4

Updated by Steffen Zieger over 11 years ago

Check if the assignee field is required in your workflow.

For example:
Administration -> Workflow
Select a role and the tracker of your ticket and click on edit. After that select "Fields permissions" tab and check if assignee field has a value of required.

Actions
Copy link
 #5

Updated by chris p over 11 years ago

Hi Steffen, thank you for the response, I don't have anything set for any of those field and I've been through all the role & tracker variations possible.

I can see there is a read-only and required option but all are blank?

Actions
Copy link
 #6

Updated by Toshi MARUYAMA over 11 years ago

  • Category changed from Email notifications to Email receiving
Actions
Copy link
 #7

Updated by Matt Fozard about 10 years ago

We've got the "Assignee can't be blank" problem too, and I've just discovered that it's a bug in the ekanban plugin that you're also using. See https://github.com/samchen2009/ekanban/issues/23

Cheers, Matt

Actions
Copy link
 #8

Updated by Toshi MARUYAMA about 10 years ago

  • Status changed from New to Closed

If you still have problem without ekanban plugin, please reopen.

Actions
Copy link
 #9

Updated by Zoltán Sinkovicz over 9 years ago

I've got the "Validation failed: Assignee can't be blank" problem.

I use this:

Environment:
Redmine version 2.6.3.stable
Ruby version 2.0.0-p384 (2014-01-12) [x86_64-linux-gnu]
Rails version 3.2.21
Environment production
Database adapter Mysql2
SCM:
Subversion 1.8.8
Git 1.9.1
Filesystem
Redmine plugins:
redmine_checklists 3.0.2
redmine_default_assign 0.4
redmine_my_page_queries 2.1.6
redmine_watcher_groups 0.0.3git
redmine_wktime 1.7

Actions
Copy link
 #10

Updated by Toshi MARUYAMA about 9 years ago

Zoltán Sinkovicz wrote:

I've got the "Validation failed: Assignee can't be blank" problem.

Do not post to unrelated issue.
Try without plugins.
If you still have problems without plugins, please create new issue.

Actions
Copy link

Also available in: Atom PDF