Misc tech notes

From UG

Revision as of 23:35, 31 July 2011

Data transfer in Navicat

• Services:
  • My Computer > Right click > MAnage...

• Data transfer through Navicat

Tools > DAta Transfer
In this order:
- tables, proc, views (several times until no errors)
(set Tools > DAta Transfer > Advanced > continue on errors = check)

webapps location on .6

/opt/apache-tomcat-5.5.27/webapps/

Misc

• mysqldump --help

mantis config strings

array(selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment, status, last_updated, custom_CT2comp, custom_Rel.Date, summary)

array(selection, status, custom_T,custom_ds, custom_emh, custom_due, id, summary)

array(selection, custom_state, status, custom_tag0, custom_T, custom_ds, custom_emh, custom_due, id, summary)

array(custom_state, status, custom_Watch, custom_T, custom_ds, custom_emh, custom_due, selection, edit, id, custom_comp, summary)

array(custom_state, status, custom_D, custom_Watch, custom_T, custom_ds, custom_emh, custom_due, selection, edit, id, custom_comp, summary)

array(custom_state, status, custom_D, custom_Watch, custom_T, custom_ds, custom_emh, custom_m/h, custom_due, selection, edit, id, custom_comp, summary)

array(project_id, custom_state, status, custom_D, custom_Watch, custom_T, custom_ds, custom_emh, custom_m/h, custom_due, selection, edit, id, custom_comp, summary)

Mantis wiki: Customizing Columns in View Issues Page

Introduction

This recipie explains how to customize the columns to be viewed in the View Issues page. In the case where a column is specified in the list of columns to be viewed, but the code determines that such field is not applicable or is turned off via configuration, the column won't be viewed.

Column Names

Following is a list of columns to select from:

 * selection - The tick box that allows the selection of the bugs to perform a group operation on.
 * edit - The pen that allows opening an issue in Edit mode.
 * id - The issue id.
 * project_id - The project name
 * duplicate_id - The id of the last duplicate set for an issue.
 * reporter_id - The reporter of the issue.
 * handler_id - The handler of the issue (i.e. the person assigned the issue).
 * priority - The issue priority.
 * reproducibility - The issue reproducibility.
 * projection - The issue projection.
 * eta - The issue fix eta.
 * resolution - The issue resolution.
 * target_version - The issue target version.
 * fixed_in_version - The issue fixed in version.
 * view_state - The issue view state (private vs. public).
 * os - The OS to which the issue applies.
 * os_build - The OS Build to which the issue applies.
 * platform - The platform to which the issue applies.
 * version - The product version to which the issue applies.
 * attachment - The column that identifies whether an issue has attachments.
 * category - The issue category.
 * severity - The issue severity.
 * status - The issue status.
 * last_updated - The issue last updated time stamp.
 * summary - The issue summary.
 * bugnotes_count - The number of notes associated with the issue.
 * custom_xyz - Custom field with name "xyz".

Fields viewed by default

Following are the fields that are viewed by default:

 * selection
 * edit
 * priority
 * id
 * sponsorship_total - this field won't be shown if 'enable_sponsorship' configuration option is set to OFF.
 * bugnotes_count
 * attachment - this field won't be shown if 'show_attachment_indicator' configuration option is set to OFF.
 * category
 * severity
 * status
 * last_updated
 * summary

Using Custom Functions

In versions prior to 1.1.0a1, using custom functions was the only option to customize the columns to be viewed in View Issues page. For more details about this option this [entry].

Using Configuration

In Mantis 1.1.0a1, support was implemented to allow customizing the columns to be viewed via the configuration. This in addition to web based configurations allows a very easy way to configure the columns to be viewed for all projects, for a specific project, for a specific user, or for a user/project combination.

 * Click "Manage" from Main Menu.
 * Click "Manage Configuration" from "Manage" sub-menu.
 * "Configuration Report" will be selected by default.
 * Scroll to the form at the bottom of the page.
 * Select the user to which the change applies or "All Users".
 * Select the project to which the change applies or "All Projects".
 * Type "view_issues_page_columns" in the "configuration option" field.
 * Leave "Type" field set to "Default".
 * Set the "Value" field to an array of the column names to be shown.  See "Column Names" section for a complete list of options.  An example:

array ( 'selection', 'edit', 'priority', 'id', 'sponsorship_total', 'bugnotes_count', 'attachment', 'category', 'severity', 'status', 'last_updated', 'summary' );

 * Click "Set Configuration Option".

Changes in 1.1.2

The "Manage Configuration" page has changed behaviour in 1.1.2 because of the the security fix detailed in [8976]

The correct value to use for the above example starting from 1.1.2 is: array( selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment, category, severity, status, last_updated, summary )

With proj id

array( selection, edit, priority, id, sponsorship_total, bugnotes_count, attachment, category, severity, status, last_updated, summary )

array (project_id, custom_state,status,custom_D,custom_Watch, custom_T, custom_ds, custom_emh, custom_m/h, custom_due, selection, edit, id, custom_comp, summary,)

mar 11 2010

array(project_id, custom_state, status, custom_D, custom_Watch, custom_T, custom_ds, custom_Risk, custom_emh, custom_m/h, custom_due, selection, edit, id, custom_comp, summary)

Design

array (status, custom_T, custom_Dz.emh, custom_Dz.amh, custom_Dz.rmh, custom_due, selection, edit, id, custom_comp, summary)

All Projects

array(status, custom_pPM, custom_pMO, custom_pBA, custom_pSA, selection, edit, id, summary)

Demo

array(status, custom_T, selection, edit, id, custom_comp, summary)

Resources

array(custom_.j05,custom_.j12, custom_.j19, custom_.j26,custom_.a02, custom_.a09, custom_.a16, custom_.a30,selection, edit, id, custom_Resource, summary)

Estim

array(status, custom_T, custom_ds, custom_due, custom_Risk, custom_emh, custom_emhR, selection, edit, id, custom_projID, custom_comp, summary)

Implem

array(summary, id, project_id, status, custom_T, selection, edit, custom_projID, custom_comp, custom_emh, custom_emhR, custom_rmh)

Req Dez

array(status, custom_T, custom_Rq.emh, custom_Rq.emhR, custom_Rq.amh, custom_Rq.rmh, selection, edit, id, custom_projID, custom_comp, summary)

array(status, custom_T, custom_Rq.emh, custom_Rq.emhR, custom_Rq.amh, custom_Rq.rmh, selection, edit, id, custom_projID, custom_comp, summary)

All proj

array(project_id, selection, edit, custom_pplan, custom_projID, custom_comp, summary, id, status, custom_T, custom_ppEmh)

Estim

array(status, custom_T, custom_ds, custom_due, custom_Risk, custom_emh, custom_emhR, selection, edit, id, custom_projID, custom_comp, summary)

Projects

array(status, custom_p.PM, custom_1, custom_2,custom_3,custom_4,custom_5,custom_6,custom_7,custom_8,custom_9,custom_10, custom_11,custom_12, selection, edit, id, custom_comp, custom_projID, summary)

array(custom_T, custom_BPemh, custom_p.PM, custom_1, custom_2,custom_3,custom_4,custom_5,custom_6,custom_7,custom_8,custom_9,custom_10, custom_11,custom_12, selection, edit, id, custom_comp, custom_projID)

BASA Sprint

array(status, custom_T, project_id, custom_projID, custom_comp, selection, edit, id, summary)

array(project_id, custom_BASAspr#, status, custom_T, custom_p.BA, custom_p.SA, custom_p.Dev, custom_%BA, custom_%SA, custom_comp, selection, edit, id, summary)

DevEst

array(custom_DevSpr#, status, custom_T, custom_p.BA, custom_p.SA, custom_p.Dev, custom_.emh, custom_.emhR, custom_.rmhR, custom_comp, selection, edit, id, summary)

Dev Sprint

array(project_id, status, custom_T, custom_p.BA, custom_p.SA, custom_p.Dev, custom_.emh, custom_.emhR, custom_.rmhR, custom_%UAT, custom_%WU, custom_comp, selection, edit, id, summary)

IT support

array(status, priority, date_submitted, category, reporter_id, selection, edit, id, summary)

Sys Adm

array(status, priority, date_submitted, category, reporter_id, custom_.emh, custom_.m/h, selection, edit, id, summary)

array(project_id, status, custom_T, custom_p.BA, custom_p.SA, custom_p.Dev, custom_.emh, custom_.emhR, custom_.rmhR, custom_%UAT, custom_%WU, custom_comp, selection, edit, id, summary)

Sup Inbox

array(status, custom_T, custom_comp, selection, edit, id, summary)

Dev Est/Sprint

array(project_id, status, custom_T, custom_p.BA, custom_.emh, custom_.emhR, custom_.rmhR, selection, edit, id, summary)

BA projects

Status T p.BA .emh .emhR .rmhR ID Summary

array(status, custom_T, custom_p.BA, custom_BA.emh, custom_BA.emhR, custom_BA.rmhR, selection, edit, id, summary)

Projects

array(status, custom_T, custom_p.PM, custom_p.BA, custom_p.Dev, custom_p.Dev2, custom_.emh, custom_.emhR, custom_.rmhR, selection, edit, id, summary)

array(custom_T, custom_p.PM, custom_p.BA, custom_p.Dev, custom_p.Dev2, custom_p.Dev3, custom_.emh, custom_.emhR, custom_.rmhR, selection, edit, id, summary)

Subcomps

array(status, category, custom_T, custom_p.MO, custom_p.BA, custom_p.Dev, selection, edit, custom_comp, id, summary)

array(status, custom_phase, custom_T, custom_p.MO, custom_p.BA, custom_p.Dev, custom_.emh, custom_.emhR, selection, edit, id, custom_comp, summary)

CT2 map

array(status, custom_T, custom_p.MO, custom_p.BA, custom_p.Dev, selection, edit, id, custom_comp, summary)