#SCB3019 (Unconfirmed) Connot edit default data for attribute groups.
Johannes Hoechstaedter <[email protected]> Fri, 12 Feb 2010 09:53:00 +0100 (CET)
| Newsgroups | gmane.comp.java.scarab.issues |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_22442_14461907.1265964785718
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
*SCB3019 [Defect] - Connot edit default data for attribute groups.*
** null: () **
-------------------------------------------------------------------------------
*Attribute changes*
-------------------------------------------------------------------------------
- Summary: Connot edit default data for attribute groups. (New)
- Priority: 3-Normal (New)
- Target milestone: 0.22 (New)
- Version: trunk (New)
- Status: Unconfirmed (New)
- Short description:
"The default data for "scarab_attribute_group"
is not visible after a fresh install in the UI. I can create a new
module, which inherits the attribute groups correctly from the global
definitions, but as said, I can't see the global attributegroups in the
UI, and thus they can't be edited.
"
-------------------------------------------------------------------------------
*Comments*
-------------------------------------------------------------------------------
*Comment Johannes Hoechstaedter*
As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
-------------------------------------------------------------------------------
*Comment Johannes Hoechstaedter*
As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
-------------------------------------------------------------------------------
*Comment Johannes Hoechstaedter*
As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
-------------------------------------------------------------------------------
*Comment Johannes Hoechstaedter*
As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
-------------------------------------------------------------------------------
Activity generated by Johannes Hoechstaedter ([email protected]) at 02/12/2010 09:43
[Scarab]: http://www.solitone.org/scarab/issues/id/SCB3019
------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=2447015
To unsubscribe from this discussion, e-mail: [[email protected]].
------=_Part_22442_14461907.1265964785718
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN"
"http://www.solitone.org/scarab/style/tigris_transitional.dtd">
<html>
<head>
<title>Activity report on Defect SCB3019 - Connot edit default data for attribute groups.</title>
<base href="http://www.solitone.org/scarab" />
<meta http-equiv="Content-type" content="text/html; charset=UTF-8" />
<style type="text/css">
body {
background: #fff;
color: #000;
}
.app h3, .functnbar {
background-image: url(http://www.solitone.org/scarab/images/nw_maj_rond.gif);
background-repeat: no-repeat;
}
.functnbar, .functnbar2 {
background-color: #aaa;
}
.functnbar2 {
background-color: #aaa;
background-image: url(http://www.solitone.org/scarab/images/sw_maj_rond.gif);
background-repeat: no-repeat;
background-position: bottom left;
}
.functnbar, .functnbar2 {
color: #000;
}
.functnbar a, .functnbar2 a {
color: #000;
text-decoration: underline;
}
.app h3 {
color: #fff;
background-color: #333;
}
.odd td {
background: #ddd;
}
.even td {
background: #efefef;
}
table, th, td {
border: none;
}
#breadcrumbs {
text-decoration: none;
border-top: 1px solid #fff;
background-color: #ccc;
}
.app th {
background-color: #bbb;
}
.infomark {
background: url(http://www.solitone.org/scarab/images/icon_info_sml.gif) top left no-repeat;
font-style: italic;
padding-left: 20px;
min-height: 15px;
}
.url {
align: left;
padding-right: 40px;
min-height: 15px;
text-decoration: underline;
color: blue;
background: url(http://www.solitone.org/scarab/images/icon_url.gif) top right no-repeat;
}
body, th, td {
font-family: Verdana, Helvetica, Arial, sans-serif;
}
pre {
font-family: 'Andale Mono', Courier, monospace;
font-size: small;
}
body, .app h3 {
font-size: small;
}
.functnbar {
font-size: x-small;
}
p {
margin-top: .67em;
margin-bottom: .67em;
}
h3 {
margin-bottom: 0;
}
.app h3 {
padding: 5px;
margin-right: 2px;
margin-left: 2px;
}
.app td, .app th {
padding: 2px 2px;
}
.h3 p {
margin-right: 7px;
margin-left: 7px;
}
.functnbar, .functnbar2 {
padding: 5px;
margin: .67em 2px;
}
body {
padding: 1em;
}
th, td {
text-align: left;
vertical-align: top;
}
.axial th {
text-align: right;
}
.app .axial td th {
text-align: left;
}
.axial th {
width: 12em;
}
.app h3 {
clear: both;
}
.app h3, #banner, #banner td {
background-color: #036;
color: #fff;
}
#banner {
border-top: 1px solid #369;
}
.functnbar2 {
background-image: url(http://www.solitone.org/scarab/images/sw_maj_rond.gif);
background-repeat: no-repeat;
background-position: bottom left;
background-color: #668DB2;
color: #fff;
margin-left: -1px;
margin-right: -1px;
white-space: nowrap;
margin-bottom: 0px;
}
.functnbar {
background-color: #668DB2;
color:#fff;
white-space:nowrap;
margin-bottom:0px;
margin-left:-1px;
margin-right:-1px;
}
.scarab-canvas {
border-width:1px;
border-style:solid;
border-color:#dddddd;
border-top-style:none;
border-bottom-style:none;
margin-left:2px;
margin-right:2px;
}
.scarab-canvas div h3 {
background-color:#E9F1F9;
color:#003163
}
.app h3, .functnbar {
background-image: url(http://www.solitone.org/scarab/images/nw_maj_rond.gif);
background-repeat: no-repeat;
}
.app h3 {
color: #003366;
background-color: #ABC4DB;
}
.app h3 a:link, .app h3 a:visited {
color: #003366 !important;
text-decoration: underline;
}
.axial th {
background-color: #E9F1F9;
color: black;
}
</style>
<link rel="stylesheet" type="text/css" href="/skins/print.css" media="print" />
</head>
<body>
<div id="scb_banner">
<table border="0" cellspacing="0" cellpadding="8" width="100%">
<tr>
<td>
<img src="http://www.solitone.org/scarab/images/logo.gif" alt="Scarab" width="118" height="23" border="0" />
</td>
<td valign="middle">
<table border="0" cellpadding="0" cellspacing="0">
<td>The Self Issue Tracker</td>
<td>
<img hspace="10" src="http://www.solitone.org/scarab/images/trans.gif" border="0"/>
</td>
</table>
</td>
</tr>
</table>
</div>
<div id="breadcrumbs" >
<table border="0" cellspacing="0" cellpadding="8" width="100%">
<tr>
<td>
Modules >
Scarab >
Issue <strong>SCB3019</strong> (<strong>Connot edit default data for attribute groups.</strong>)
</td>
</tr>
</table>
</div>
<div class="app">
<p class="infomark">
Activity generated by
Johannes Hoechstaedter ([email protected]) at 02/12/2010 09:43
</p>
<div class="scarab-canvas">
<h3 class="functnbar" style="background-color: #668DB2;margin-left:-1px;margin-right:-1px;">
<strong>Issue <strong>SCB3019 </strong>(<strong>Connot edit default data for attribute groups.</strong>)
</h3>
<h3>Attributes</h3>
<div class="axial">
<table>
<tr>
<th>Issue ID</th>
<td width="25%"><b>SCB3019 (Defect)</b></td>
<td>
</td>
</tr>
<tr>
<th>Created by</th>
<td colspan="2">
<a href="mailTo:[email protected]">Johannes Hoechstaedter</a>
Fri Feb 12 09:43:30 CET 2010
</td>
</tr>
<tr>
<th>Last modified by</th>
<td colspan="2">
<a href="mailTo:[email protected]">Johannes Hoechstaedter</a>
2010-02-12 09:47:30.0
</td>
</tr>
</table>
</div>
<h3>Summary of activity</h3>
<div class="axial">
<table style="table-layout: fixed" width="100%">
<tr class="even">
<th rowspan="1" width="25%">Issue general information</th>
<td>null: ()</td>
</tr>
<tr class="odd">
<th rowspan="6" width="25%">Attribute changes</th>
<td>Summary: Connot edit default data for attribute groups. ()</td>
</tr>
<tr class="even">
<td>Priority: 3-Normal ()</td>
</tr>
<tr class="odd">
<td>Target milestone: 0.22 ()</td>
</tr>
<tr class="even">
<td>Version: trunk ()</td>
</tr>
<tr class="odd">
<td>Status: Unconfirmed ()</td>
</tr>
<tr class="even">
<td>"Short description" set to: "The default data for "scarab_attribute_group"
is not visible after a fresh install in the UI. I can create a new
module, which inherits the attribute groups correctly from the global
definitions, but as said, I can't see the global attributegroups in the
UI, and thus they can't be edited.
"</td>
</tr>
<tr class="odd">
<th rowspan="8" width="25%">Comments</th>
<td>By <a href="mailTo:[email protected]">Johannes Hoechstaedter</a>
02/12/2010 09:46</td>
</tr>
<tr class="even">
<td><pre>As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
</pre></td>
</tr>
<tr class="odd">
<td>By <a href="mailTo:[email protected]">Johannes Hoechstaedter</a>
02/12/2010 09:47</td>
</tr>
<tr class="even">
<td><pre>As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
</pre></td>
</tr>
<tr class="odd">
<td>By <a href="mailTo:[email protected]">Johannes Hoechstaedter</a>
02/12/2010 09:47</td>
</tr>
<tr class="even">
<td><pre>As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
</pre></td>
</tr>
<tr class="odd">
<td>By <a href="mailTo:[email protected]">Johannes Hoechstaedter</a>
02/12/2010 09:47</td>
</tr>
<tr class="even">
<td><pre>As I found out, for module_id in "scarab_attribute_group" "null" values
are supported since introduction for global issue types (e.g. see file
scarab_schema.xml, revision 5670 line 282). In "scarab_attribute_group"
"null" is used for attribute "module_id" for the global data if the
attribute group is created via UI. But there is, historically(?), the id
"0", which stands for the global module too?
I found out that not in every case the global module id is handled as
"null", in general scarab supports both, "0" and "null". (see other tables in scarab's database)
In default data the value for the attribute groups is "0". That's what's
causing the issue.
Question: Should both 0 and "null" be supported, or is there a long term
goal to unifiy this? Our preference would be "0".
Possible current fixes will be:
1. Change the default data to use "null" (see question above?) - not preferred
2. Implement the attribute_group uses "0" (see file IssueType.java, revision 8711, line 412) - preferred
3. Implement the attribute_group uses both "0" and "null" (see file
IssueType.java, revision 8711, line 412) - not preferred, but maybe
safer than 2.
Additionally, 2 would need attention for the database update scripts, as
it seems there are mixed value in the databases around/in use. Maybe
some can check this on his installation.
</pre></td>
</tr>
</table>
</div>
<div class="functnbar2"">
<table>
<tr>
<td>
<div class="url">
<a title="Bookmark to this issue" href="http://www.solitone.org/scarab/issues/id/SCB3019">
Session-info-free link to SCB3019</a>
</div>
</td>
</tr>
</table>
</div>
</div>
</div>
</body>
</html>
------=_Part_22442_14461907.1265964785718--