[#JRA-12773] Please make a custom field required without a "none" option on the resolve screen

JIRA

Please make a custom field required without a "none" option on the resolve screen

Created: 22/May/07 08:55 AM Updated: 13/Nov/07 06:56 PM

Component/s:

Workflow, Administration, Custom Fields

Affects Version/s:

3.8.1 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

microsoft windows server 2003

Issue Links:

Reference

This issue relates to:

JRA-5783 Make field required only for one state transition

Participants:	Anton Mazkovoi [Atlassian], Jeff Schnitter and LERZAN SENCER
Since last comment:	25 weeks, 6 days ago
To be done by:	Pair of developers
Labels:

Description

« Hide

Hello dear JIRA team,

I want to have a custom field required also without a "none" option on the resolve screen.
Below are my requirements for a custom field for which 4 of them should be maintained at the same time
1) The custom field to be required
2) The custom field not to have a "none" option
3) The custom field to be on the resolve screen
4) The custom field to not effect submit screen or other screens which does not have this custom field

If I make the custom field "required", then the submit screen does not allow me to make a transition without filling this required custom field although it belongs to the resolve screen.
So, I downloaded the extension "Workflow Validator to require a field on a transition screen" and make the custom field "optional". The problem of transition is fixed but a "none" option appears for this field value on the resolve screen.

Please help me

Thanks and Best regards,

Lerzan Sencer

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 22/May/07 09:19 PM

Hi,

Am I right in believing that if we do implement JRA-5783, you will no longer need this featur?

Cheers,
Anton

[ Permlink | « Hide ]

LERZAN SENCER - 23/May/07 01:02 AM

Hi Anton,

If you implent JRA-5783 I will no longer need this feature but the "Workflow Validator plugin" does not resolve my problem as I suggested in the description part. Custom fields should be set as required or optional for different screens and without a "none" option.

Thanks

Lerzan

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 23/May/07 01:57 AM

Hi,

Thanks for the update.

Am I right in understanding that at the moment, the validator does stop the user from selecting the "none" option from the custom field. It's just quite annoying that the "none" option is there, and that the user is prompted with an error if they leave the custom field set to none?

Cheers,
Anton

[ Permlink | « Hide ]

LERZAN SENCER - 23/May/07 02:04 AM

Exactly Anton ! And I would mention one more time that the required custom fields should be available for different screens.

Thanks

Lerzan

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 23/May/07 02:17 AM

Hi Lerzan,

Thanks for clarifying the situation.

And I would mention one more time that the required custom fields should be available for different screens.

Do you mean that it should be possible to make a screen required on a worklow transition, e.g. Resolve Issue, such that the field is not required during issue creation?

Please vote for JRA-5783 as given the number of feature requests that we have, we are much more likely to attack JRA-5783 before this issue.

Cheers,
Anton

[ Permlink | « Hide ]

LERZAN SENCER - 23/May/07 02:31 AM

Anton,

Thanks for the quick response

I've already voted for JRA-5783. I hope this issue will be solved as soon as possible.

Thank you

Lerzan

[ Permlink | « Hide ]

Jeff Schnitter - 13/Nov/07 01:46 PM

I see that there are a handful of issues dealing with the value 'None' in custom fields. My .02 – if you make a custom field required 'None' still appears in the drop down list, but it isn't a valid choice. You correctly get an error that the field is required. If the choice 'None' isn't valid for required fields it should not be presented as a choice to the user.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 13/Nov/07 06:56 PM

Jeff,

A lot of users actually would like 'None' to appear in the list even if the field is required, as they want a user to make a conscious choice and select a value.

If a custom field is required and has a default value, the 'None' option should disappear. I believe this is how things work at the moment.

Cheers,
Anton