[jira] Updated: (OFBIZ-2312) Styling flaws in smoothfeather

2009-04-17 Thread Jacques Le Roux (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-2312:
---

Description: 
I was to create an issue for each styling flaws in smoothfeather, but it's far 
too mcuh work. So I have created only one issue to list what we find.
We can create a numbered comment for each issue to separate them and refer 
easily to them whe fixed. Here we go

I wondered how to close (sub-)issues here. I thought about removing comments 
but  using -understrike- with a notice should be far better. You get  
-understrike- using \-understrike\-


  was:
I was to create an issue for each styling flaws in smoothfeather, but it's far 
too mcuh work. So I have created only one issue to list what we find.
We can create a numbered comment for each issue to separate them and refer 
easily to them whe fixed. Here we go


 Styling flaws in smoothfeather
 --

 Key: OFBIZ-2312
 URL: https://issues.apache.org/jira/browse/OFBIZ-2312
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: SVN trunk
 Environment: XP FF3
Reporter: Jacques Le Roux
 Fix For: SVN trunk


 I was to create an issue for each styling flaws in smoothfeather, but it's 
 far too mcuh work. So I have created only one issue to list what we find.
 We can create a numbered comment for each issue to separate them and refer 
 easily to them whe fixed. Here we go
 I wondered how to close (sub-)issues here. I thought about removing 
 comments but  using -understrike- with a notice should be far better. You get 
  -understrike- using \-understrike\-

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (OFBIZ-2312) Styling flaws in smoothfeather

2009-04-17 Thread Jacques Le Roux (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacques Le Roux updated OFBIZ-2312:
---

Description: 
I was to create an issue for each styling flaws in smoothfeather, but it's far 
too mcuh work. So I have created only one issue to list what we find.
We can create a numbered comment for each issue to separate them and refer 
easily to them whe fixed. Here we go

I wondered how to close (sub-)issues here. I thought about removing comments 
but editing the original comment and  using -understrike- with a notice should 
be far better. You get  -understrike- using \-understrike\-

If someone feels that the sub-issues here should be splitted in standard 
sub-tasks of OFBIZ-2309 (or even better of the current issue), please feel free 
to do so 


  was:
I was to create an issue for each styling flaws in smoothfeather, but it's far 
too mcuh work. So I have created only one issue to list what we find.
We can create a numbered comment for each issue to separate them and refer 
easily to them whe fixed. Here we go

I wondered how to close (sub-)issues here. I thought about removing comments 
but editing the original comment and  using -understrike- with a notice should 
be far better. You get  -understrike- using \-understrike\-

If someone feels that the sub-issues here should be splitted in standard 
sub-tasks of OFBIZ-2309, please feel free to do so 



 Styling flaws in smoothfeather
 --

 Key: OFBIZ-2312
 URL: https://issues.apache.org/jira/browse/OFBIZ-2312
 Project: OFBiz
  Issue Type: Sub-task
Affects Versions: SVN trunk
 Environment: XP FF3
Reporter: Jacques Le Roux
 Fix For: SVN trunk


 I was to create an issue for each styling flaws in smoothfeather, but it's 
 far too mcuh work. So I have created only one issue to list what we find.
 We can create a numbered comment for each issue to separate them and refer 
 easily to them whe fixed. Here we go
 I wondered how to close (sub-)issues here. I thought about removing 
 comments but editing the original comment and  using -understrike- with a 
 notice should be far better. You get  -understrike- using \-understrike\-
 If someone feels that the sub-issues here should be splitted in standard 
 sub-tasks of OFBIZ-2309 (or even better of the current issue), please feel 
 free to do so 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.