Difference between revisions of "Documentation/Nightly/Developers/BugTrackerConfiguration"
From Slicer Wiki
m |
|||
Line 30: | Line 30: | ||
* Value: <code>array ( selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment, category, severity, reporter_id, status, last_updated, summary ) </code> | * Value: <code>array ( selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment, category, severity, reporter_id, status, last_updated, summary ) </code> | ||
− | + | {{remark|red|'''category''' should be used instead of '''category_id'''}} | |
− | |||
− | |||
Revision as of 22:55, 21 June 2016
Home < Documentation < Nightly < Developers < BugTrackerConfiguration
For the latest Slicer documentation, visit the read-the-docs. |
This page documents the tweak and configuration details specific to Slicer bug trackers.
Allow Reporter, updater, developer to add notes even if issue is resolved or closed
In Manage -> Manage Projects -> Slicer4 -> Manage Configuration -> Configuration Report
Add a new entry:
* Username: All Users * Project: Slicer4 * Configuration Option: update_readonly_bug_threshold * Type: integer * Value: 25 * Access Level: administrator
References:
- http://www.mantisbt.org/forums/viewtopic.php?f=3&t=105
- http://www.mantisbt.org/manual/manual.page.descriptions.system.management.pages.manage.configuration.workflow.thresholds.php
- http://www.mantisbt.org/docs/master/en/administration_guide/admin.user.access.html
Add Reporter field in the View Issues page
In Manage -> Manage Configuration -> Configuration Report
Then, in "Set Configuration Option":
- Username: All users
- Project name: Slicer4
- Configuration Option: view_issues_page_columns
- Type: default
- Value:
array ( selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment, category, severity, reporter_id, status, last_updated, summary )
- category should be used instead of category_id
.. and click on "Set Configuration Option"
References: