New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-5943
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Neal Applebaum
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Allow required hidden fields when default value set

Created: 15/Feb/05 03:22 PM   Updated: 08/Apr/05 07:26 AM
Component/s: Permissions Security
Affects Version/s: 3.0.3
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Jeff Turner [Atlassian] and Neal Applebaum
Since last comment: 3 years, 19 weeks, 1 day ago
Labels:


 Description  « Hide
I couldn't figure out how to hide the security field and still have it default to the only valid security level.

I set it to Required, and hidden, but when issues were added (by me), the security level was recorded as "None".

It looks like I had 2 choices to resolve this:

1) unhide the field in order to get it to set the security level to the only valid choice
2) set the permission scheme so that the person entering the issue (me) cannot also set issue security

I went with option 2..

Do you think that's a bug? i.e. just because I have issue security permissions doesn't mean it shouldn't still pick up the default security level when the field is hidden.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] added a comment - 18/Feb/05 12:57 AM
Neal,

If the security level field is marked as 'Required', then the 'None' option should disappear. That it doesn't is a bug:

http://jira.atlassian.com/browse/JRA-5332

I'm not sure I've understood the situation properly. If JRA-5332 was fixed, would that address this issue?

Cheers,
Jeff


Neal Applebaum added a comment - 21/Feb/05 07:34 AM
Certainly JRA-5332 is related, because I agree that 'None' should not be presented as an option if it cannot be selected. However, my problem is that when the field is hidden, it actually DOES record None as the security level. Please try this and let me know if you can or cannot reproduce. That is - set it to required and hidden, and see what it records as the security level.

Jeff Turner [Atlassian] added a comment - 07/Mar/05 10:05 PM
"Required" and "hidden" are mutually exclusive - you cannot have both selected in the JIRA interface. I assume you have 'hidden' set, so the field is actually not required. I've updated the issue subject - is this a correct summary of what you're after?

Neal Applebaum added a comment - 08/Apr/05 07:26 AM
I guess..