View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023363 | mantisbt | other | public | 2017-09-15 12:14 | 2017-09-29 02:46 |
Reporter | helfy022 | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Product Version | 2.5.1 | ||||
Summary | 0023363: mantis_category_table status field | ||||
Description | Hello, What is the purpose of the status field in the mantis_category_table?
Thanks, | ||||
Tags | No tags attached. | ||||
I has a short look and did not find any usage of this field in current code. helfy022, This is not a bug or feature request for MantisBT (you are asking for internal technical details of the system). I am therefore resolving this issue as "no change required". Please use the forums to get support on customizing and using MantisBT (refer to http://www.mantisbt.org/support.php for links and further details). |
|
Hi Atrol, Thanks for clarifying. Please feel free to close. Ryan. |
|
@helfy022 it was part of the original spec for this feature's implementation but the purpose of the field was never documented |
|
Thanks for the clarification. One quick aside, if I may. I noticed that the Description shows the SQL STDOUT table I posted to be nicely formatted. When we create issues/notes with such SQL output copy/pasted, we find the formatting to not be preserved. In particular, in the Description and Notes, the whitespace used to keep the table formatting gets dropped. How can we tune our config to ensure that the View Issue Details page will show the nice table formatting as is shown above. Thanks, |
|
You have to enable Markdown in configuration of Mantis Core Formatting plugin. |
|
This is the experimental markdown formatting feature, which is disabled by default. If you don't want to enable it you can also use html |
|