自定义 Mantisbt 的问题字段和转换

发布于 2024-12-13 07:40:38 字数 177 浏览 4 评论 0原文

我正在开发 Mantisbt 1.2.8，我正在尝试自定义问题创建时显示的字段。到目前为止，我已经能够添加字段，但无法删除/隐藏默认字段。
我找不到教程（对于傻瓜，jeje）一步一步的解释，显示为：
1。如何在创建问题时具体设置字段以及
2。如何定义自定义工作流程状态和转换。

我真的很感谢一些帮助。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

好倦 2024-12-20 07:40:38

您可以在 config_inc.php 文件中定义字段和工作流程状态/转换。

如 config_defaults_inc.php 中所述（此文件中有很多有用的信息）

/**
* 'status_enum_workflow' defines the workflow, and reflects a simple
*  2-dimensional matrix. For each existing status, you define which
*  statuses you can go to from that status, e.g. from NEW_ you might list statuses
*  '10:new,20:feedback,30:acknowledged' but not higher ones.
* The following example can be transferred to config_inc.php
* $g_status_enum_workflow[NEW_]='20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved';
* $g_status_enum_workflow[FEEDBACK] ='10:new,30:acknowledged,40:confirmed,50:assigned,80:resolved';
* $g_status_enum_workflow[ACKNOWLEDGED] ='20:feedback,40:confirmed,50:assigned,80:resolved';
* $g_status_enum_workflow[CONFIRMED] ='20:feedback,50:assigned,80:resolved';
* $g_status_enum_workflow[ASSIGNED] ='20:feedback,80:resolved,90:closed';
* $g_status_enum_workflow[RESOLVED] ='50:assigned,90:closed';
* $g_status_enum_workflow[CLOSED] ='50:assigned';
* @global array $g_status_enum_workflow
*/

和

/**
* An array of the fields to show on the bug report page.
*
* The following fields can not be included:
* id, project, date_submitted, last_updated, status,
* resolution, tags, fixed_in_version, projection, eta,
* reporter.
*
* The following fields must be included:
* category_id, summary, description.
*
* To overload this setting per project, then the settings must be included in the database through
* the generic configuration form.
*
* @global array $g_bug_report_page_fields
*/

You can define fields and workflow states/transitions in your config_inc.php file.

As documented in config_defaults_inc.php (lots of good info in this file)

/**
* 'status_enum_workflow' defines the workflow, and reflects a simple
*  2-dimensional matrix. For each existing status, you define which
*  statuses you can go to from that status, e.g. from NEW_ you might list statuses
*  '10:new,20:feedback,30:acknowledged' but not higher ones.
* The following example can be transferred to config_inc.php
* $g_status_enum_workflow[NEW_]='20:feedback,30:acknowledged,40:confirmed,50:assigned,80:resolved';
* $g_status_enum_workflow[FEEDBACK] ='10:new,30:acknowledged,40:confirmed,50:assigned,80:resolved';
* $g_status_enum_workflow[ACKNOWLEDGED] ='20:feedback,40:confirmed,50:assigned,80:resolved';
* $g_status_enum_workflow[CONFIRMED] ='20:feedback,50:assigned,80:resolved';
* $g_status_enum_workflow[ASSIGNED] ='20:feedback,80:resolved,90:closed';
* $g_status_enum_workflow[RESOLVED] ='50:assigned,90:closed';
* $g_status_enum_workflow[CLOSED] ='50:assigned';
* @global array $g_status_enum_workflow
*/

and

/**
* An array of the fields to show on the bug report page.
*
* The following fields can not be included:
* id, project, date_submitted, last_updated, status,
* resolution, tags, fixed_in_version, projection, eta,
* reporter.
*
* The following fields must be included:
* category_id, summary, description.
*
* To overload this setting per project, then the settings must be included in the database through
* the generic configuration form.
*
* @global array $g_bug_report_page_fields
*/

回复收藏 0 原文

~没有更多了~