View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0026140 | mantisbt | custom fields | public | 2019-09-14 14:55 | 2019-12-17 09:07 |
Reporter | cproensa | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 2.23.0 | ||||
Summary | 0026140: Custom fields are displayed on issue report even if they have disabled "Display When Reporting Issues" | ||||
Description | The custom fields are presented in report page when they are configured with "Display When Reporting Issues" OR "Required On Report".
In my case, i use a plugin with "report_bug_form" event to display a customized input for a required custom field, so i don't want to display the standard input. At the moment, i need a javascript routine that deletes the standard input from the form. This is a very unelegant, solution. | ||||
Tags | No tags attached. | ||||
Do you mean Display When Reporting Issues ?
Which as I recall is the reason why display was handled with OR
What do you propose ? |
|
yes, reporting. But probably it's also applicable to the other similar options.
In a similar scenario, when configuring the workflow, we display warnings for inconsistent transitions (unreachable status, etc) |
|
Another use case: |
|
@cproensa About your last case: I was stumbling across this exact same situation and we were looking for a solution, then @dregad linked me to this issue. |
|
I think that behavior makes sense, but before modifying it, we must agree for the change. |
|
@keessonnema |
|
Thanks. I will monitor the issue. |
|
Any updates on this? |
|