Set default component to empty string

[asaf.levy@…]

I am trying to set the default component to an empty string. but when ever I set the default value = to an empty value it will be set to the first on the list of components.

[Christian Boos]

Such an empty component would have to exist first, but it looks like you can't create a component with an empty name.

You could simply create a dummy component named '(none)' or '(unspecified)' and make this the default.

OTOH, it might be useful to be able to leave it really unset (especially with the 1.0 "graying out" of unspecified fields).

[Ryan J Ollos]

Replying to cboos:

OTOH, it might be useful to be able to leave it really unset (especially with the 1.0 "graying out" of unspecified fields).

This was also requested in #11300. I made the comment there that it might also make sense to allow Priority and Severity to be left unset, but maybe not for Type and Resolution.

[Ryan J Ollos]

By allowing an empty component we would also resolve an inconsistency that currently exists in that the Query page allows a Component filter with an empty value.

[Ryan J Ollos]

How about a new configuration option, [ticket] optional_fields? One potential source of confusion though is that the use of the term optional may lead some to believe that not including a field in the list will force a user to choose a selection before submitting a form, a feature which might be enforced in the future through a required option.

Proposed changes can be found in log:rjollos.git:t10772. The optional parameter is also passed to query page, and utilized in the query and batch modification forms.

For TracTicketsCustomFields, it is already possible to include an empty entry in the selections by adding a trailing |, or an empty string between a pair of pipes. I opted to add the flexibility of allowing custom fields to also be specified in [ticket] optional_fields.

In the future I'll add the functionality to allow the configuration option to be configured from the admin pages, but I'd like to complete some other changes to the admin pages before implementing that.

[Ryan J Ollos]

Committed to trunk in [12343].

[Ryan J Ollos]

Replying to rjollos:

In the future I'll add the functionality to allow the configuration option to be set from the admin pages, but I'd like to complete some other changes to the admin pages before implementing that.

Specifically, it was discussed in #7850 to move the [ticket] default_* options into the database. When that is done, we could also move the [ticket] optional_fields option to the database and add the Admin page functionality at that time.

[Ryan J Ollos]

Replying to rjollos:

Proposed changes can be found in log:rjollos.git:t10772. The optional parameter is also passed to query page, and utilized in the query and batch modification forms.

For TracTicketsCustomFields, it is already possible to include an empty entry in the selections by adding a trailing |, or an empty string between a pair of pipes. I opted to add the flexibility of allowing custom fields to also be specified in [ticket] optional_fields.

This resolves the issue reported in ​th:#10913.

[Ryan J Ollos]

I'm reconsidering the naming of this field. Maybe [ticket] allowed_empty_fields is more clear?

[Ryan J Ollos]

comment:10 change committed to trunk in [14153].