-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assignee can't be blank #23
Comments
I feel it fitting to point out that GitHub allowed me to create this issue without setting an assignee. 😏 |
Agreed that when an issue is 'new', the assignee can be blank (but I still think assigning to group is better if it's hard to determine the owner at that point), but in other status an assignee is a required to calculate WIP. This constraint was set at lib/ekanban/issue_patch.rb line 57: validates_presence_of :assigned_to. I'll perfer to make it 'required' in view. |
We found this problem while working with a project that doesn't use the plugin (it's managed in Scrum, with the Backlogs plugin) Because of this, we could not try the plugin in our setup. Our suggestion would be to only apply this validation in projects that have this plugin enabled. |
We have also hit this issue. Do you know if there's any chance of it being changed at all? Thanks! |
@dzacarias I detect the same issue using, redmine blacklogs + ekanban |
I agree dzacarias, I haven´t used this plugin because affect other projects that use Backlogs plugin, in spite of being an interesting plugin. Idem: redmine backlogs + ekanban |
We've moved on to using Trello for Kanban at our company, so this issue's no longer "pressing" for us. |
Thanks Zacarias, my company is not allowed to use another tool different Redmine :( If you know another way to configure kanban on Redmine, you will be welcome. |
I'm sorry, I haven't tried anything since moving on from this. Good luck! |
We came up with a slightly different approach – we’ve created a user of ‘Nobody Assigned’ and assign to that in order to get over the problem. Sure, it’s a bit of a fudge, but it works for us Regards - Steve From: ivansts [mailto:notifications@github.com] Thanks Zacarias, my company is not allowed to use another tool different Redmine :( If you know another way to configure kanban on Redmine, you will be welcome. — This e-mail and any files transmitted with it are confidential and If you are not the intended recipient or have received this e-mail in Whilst we have taken reasonable precautions to ensure that any A division of Rapp Limited. This email message has been delivered safely and archived online by Mimecast. For more information please visit http://www.mimecast.co.uk |
That's too bad. I've liked this plugin. But because of this problem we are using the kanban of scrum2b |
Thanks Mauro, I hadn´t taken into account. Using scrum2b could be another option. |
When creating a new issue with the ekanban plugin installed, the Assignee field becomes required, although it is not marked as such (with the red asterisk).
As a user, I'd like this field to not be required, for consistency with the standard Redmine installation. Additionally, I can set this field to required by using a custom workflow, which seems like a more flexible approach to me.
The text was updated successfully, but these errors were encountered: