User: Robert Adams | E-Mail: radams@nassco.com | Date Posted: 2005/04/26 23:39:05
Dear Colleagues,
We have discussed the sharing of data, specifically CSR data for a while, so here is one of ours to get stared.
If you agree with a CSR's purpose, the suggestion is for you to raise an additional CSR for yourself and simply refer to the original one listed here.
If you have a similar one previously raised, then let us know, this is what we seek to avoid in the future.
Best Regards,
Robert
Milko, this is a first cut of the top of my head, so feel free to rearrange things as you see fit to make maintenance easier.
Also, this is the second time I posted this, the first one went south for some reason or other ?
|
Reply
|
User: Milko Minchev | E-Mail: mbmproject@mbmproject.com | Date Posted: 2005/04/27 06:19:38
Hi Robert,
Your first post disapeared because there was an apostrophe in the topic’s name ( CSR’s ). I will try to fix this bug as soon as possible. Sorry for the inconvenience caused.
Best Regards,
Milko
|
Reply
|
User: Dragos Patilea | E-Mail: dragos.patilea@email.ro | Date Posted: 2005/04/27 06:41:56
Dear Robert, all,
May I suggest to post your CSR's with some other related data, as a subtitle, like:
- version of the Tribon (however in this case Support advise on M3SP3MU1, so I suppose that is...)
- application
- OS (sometimes this can make the difference)
just to have a quick overview?
All best,
Dragos
|
Reply
|
User: Tomasz Lisowski | E-Mail: Tomasz.Lisowski@sto-cad.com | Date Posted: 2005/04/27 08:48:31
Milko,
It seems, that for proper registering of the shared CSR information, we need a hierarchical structure of groups and topics with more than two levels. Example:
Shared CSRs (main group)
Tribon M3
General
Hull
Outfitting
...
Tribon M2
General
Hull
Outfitting
...
...
Can you forum code support this?
Tomasz
|
Reply
|
User: Milko Minchev | E-Mail: mbmproject@mbmproject.com | Date Posted: 2005/04/27 10:24:38
Dear Tomasz,
Thank you for your suggestion.
Unfortunately, for the time being we can not handle this feature. Not that it is impossible, just a matter of balance between the resources spend to handle this site and the benefit from it.
However, we might consider this as an improvement for the next, next ... service pack.
Best Regards,
Milko
|
Reply
|
User: Robert Adams | E-Mail: radams@nassco.com | Date Posted: 2005/04/27 14:26:29
Dear Milko, All,
Would CSR'''s have worked ?
Either, having no apostrophes in a title is not a problem, now we know we can just not use them.
Like Tomasz points out, having only two levels poses a hurdle, and if this can be addressed great, if not then we can work around it.
Perhaps we should remove "Shared CSR Data" from the topic title, leaving "Hull Plate Nesting CSRs" ?
Perhaps we should trim the subject title to just "CSR 35993" and simply include the normal title fields of a CSR, or at least a subset ?
COMPANY:
CONTACT PERSON:
PROBLEM TITLE:
PROBLEM TYPE:
REPRODUCIBLE:
SEVERITY:
OS-VERSION:
PRODUCT:
SYSTEM PROGRAM:
RELEASE NUMBER:
PROGRAM DATE:
But as I said at the outset, this is a first cut at it, so you slice and dice as you see fit to make forum maintenance easier.
Best regards,
Robert
|
Reply
|
User: Robert Adams | E-Mail: radams@nassco.com | Date Posted: 2005/04/27 14:59:39
All,
Where I said "Either, having no apostrophes in a title is not a problem,....", should have been "Either way, having no...." etc.
Sorry for the confusion.
|
Reply
|
User: Milko Minchev | E-Mail: mbmproject@mbmproject.com | Date Posted: 2005/04/27 16:07:50
Actually, I like the form you use in your first shared CSR. No need to copy all details from TS CSR form, I think.
May be the topic name could be: Application name (or speciality) CSRs
Then in the subject we have:
* the company name
* CSR number
* program version (SP can be added where necessary)
* CSR title
That is everything that we need to know before we click on the link to see its details.
Contact person - obviously, the person posting the message in the forum
The message body - as you have created it. We have the most important - the developers reply and the customers opinion.
Os-version could be included as well, but I do not think that it is absolutely necessary. There are number of cases when one can say for sure that the OS has nothing to do with the problem described in the CSR, so it would not be required.
It is good to have some common form of course, but there is nothing so dramatic if something a bit different is posted. The best form may come with the experience of the next CSRs posted and the following discussions may be.
Best Regards,
Milko
|
Reply
|
|
