View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0026149 | mantisbt | feature | public | 2019-09-17 03:47 | 2019-09-26 16:42 |
Reporter | keessonnema | Assigned To | dregad | ||
Priority | normal | Severity | tweak | Reproducibility | have not tried |
Status | closed | Resolution | no change required | ||
Summary | 0026149: Possibility to hide custom fields for selected users | ||||
Description | In our installation we've added some custom fields like calculations that are useful for us, but not for the client. The problem we're facing now is when we hide it on issue creation the default values won't be added inside the custom field. We need these values to easily access them when replying to the issue. | ||||
Tags | No tags attached. | ||||
related to | 0026140 | new | Custom fields are displayed on issue report even if they have disabled "Display When Reporting Issues" |
This can be achieved by specifying the appropriate access level required to read (and/or write) in custom field's definition. |
|
What I mean is that a custom-field is always empty if for example it's visible for me as a DEVELOPER, but hidden for a client (MANAGER) if the client created the issue. If someone with the correct access level creates the issue, the custom-field is filled with the default data configured in the custom-field settings. So for easy understanding I hoped for a way to only show the custom-foeld data to a specific group, but also fill the field if a client creates an issue (even though the field is not visible for them) |
|
Pre-filling custom field with default data when field is not visible at report time is a different issue. I think this is covered by an existing issue, but I don't have time to search for it now. At least this was mentioned by @cproensa in 0026140:0062805.
You have your clients as manager ? seems strange. Or did you mean reporter ? |
|
Sorry I was referring to 'updater', not 'manager'. |
|