[Solved] Clone Item - mandatory assignedto field validation

[Walter]

Hello,
we set the "assignedto" field  as mandatory. Now we cannot clone an item.
See attached screenshot.
br,
Walter

[Liliya]

Hi Walter,

Thank you for reporting this and I apologize for the inconvenience caused. We`ll include the fix in the next service pack.
I have granted you with some Telerik points for finding this problem.

Regards,
Liliya
Telerik

 

[John]

I'm curious as to why you require the assigned to field to be completed?  We leave it blank and then developers pick up items as they complete their existing item.

[Georgi]

Hi,

There is no special reasoning behind this. Just a bug on our side :)

[John]

Georgi - I understand it's a bug on your side.  I was just asking the question of Walter, as to why he sets Assigned To as required.  I'm always trying to improve our agile process and wanted to know what the thinking was behind his configuration decision.  Thanks for the quick response.

[Walter]

Hi John, 
i guess we are not typically agile. We have a business analyst (and his team) and a product advisor (and his developer team) working in teampulse. We have projects with multiple PAs and BAs, and developers do not pick an item. The PA verifies the maturity of the requirements it and assigns it to a developer in his team or re-assigns it back to the BA. Because of the various roles and the process we defined, we need to make sure that a (correct) PA is assigned initially.- Hope this clarifies it a little.