Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Default Values for project

web-app

We have added a custom field to our project that uses a text box. Now when we try to add default values for another field, this field is required. Shouldn't validation be relaxed when settting values for default fields since many will be left null?

walkerla
· 1
walkerla
Replies (5)
helpful
0
not helpful

I am not sure I understand.

You have created a text box custom field (say X) and it set to require data entry.

Now you have created default values for other fields and you do not want this field (X) to be requeired any more? correct?

If so, why make the field (X) required?

Other option is to set a default value for it (X).


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Hi

I'm having a similar problem - but no custom fields are involved. I go to Project Admin-Default values and try to set the default STATUS. When I try and save the system reports "Please select at least one component" next to the component list. I don't want to set a default component, I just want to set a default status. Why does it do this? How do I make it stop!?

Thanks


MattB
· 1
MattB
helpful
0
not helpful

The component is mandatory as every issue must be associated with a component. 
You can create a "No Component" component and default to it.


Bikram
· 1
Bikram
helpful
0
not helpful

Seems wrong to me; I agree that every issue must have an assigned Component, but that's not to say that we have to provide a default value for it (as the system currently demands). Seems as if the thinking is that the screen which accepts defaults for a Project needs defaults for everything which is mandatory - can't see the logic for having that; it should allow the Administrator to determine which fields will be defaulted and which will require user intervention before the issue gets committed, regardless of whether they're mandatory or not.

Can you confirm my understanding of your answer is correct - and if so, what's the appetite for changing it in the next release?


MattB
· 1
MattB
helpful
0
not helpful

I see your point and agree with it. Feel free to add it to our list: http://gemini.countersoft.com and we will do it for 3.6.


Mark Wing
· 9108
Mark Wing