Redmine

+1

I believe this would be a major change to Redmine but it would take it to the next level. We are currently using ClearQuest (contractual) and Redmine and one of the few things (that matter to us) that ClearQuest has that Redmine does not is to have required fields per status.

+1

+1

Required per status for all fields, not just custom fields

+1
This is very essential for use, but we already live this feature by process doc and this isn't very safe. A redmine enforced behavour would be much better.

+1
Very essential feature! I'd like to see it very soon.

+1

+1 Critical feature

+1

+1

+1

+1

+1

+1 Almost mandatory, key feature to have reliable information when >100 users

+1

Sébastien Gripon wrote:

+1

+1

+1

Note that in order to get this important feature, we have inserted javascript function that check some fields when changing the status. This is really easy to implement but should be built in redmine.

Sébastien Gripon wrote:

Note that in order to get this important feature, we have inserted javascript function that check some fields when changing the status. This is really easy to implement but should be built in redmine.

Hi Sébastien,
In case your code is re-usable, any chance to share it with us ?

Thanks Sebastien,
I should have time to take a look at it and test it on my generic environment tomorrow.
will come back thereafter :)

This is covered by #8050