Me, too.  But I have a question about the whole process.  Is there going
to be a scheduled push whether manual or automated to send the bugs to
BMC Remedy?  Would their bug number scheme be different?
How would we know if/when their fixed?

...so many questions 

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Rocky Rockwell
Sent: Friday, March 09, 2007 11:10 PM
To: [email protected]
Subject: Re: Remedy Supported Products

I would vote for it if it is not to much trouble for you.

*Rocky*

Rocky Rockwell
eMA Team - Remedy Developer
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Ph#1: 214-567-8874
Ph#2: 325-884-1263



Axton wrote:
> If there is sufficient interest, I will set it up.  The software is
> free.  Aside from periodic patches and the initial setup (backups,
> configuration, etc), the maintenance is negligable.  Plus, it would
> complement the Trac/SVN apps I have set up.
>
> Speaking of, if anyone wants to start a Remedy related development
> project (c, java, def, etc), I am open to hosting an svn repository,
> Trac interface, and maybe a bugzilla app (have to see if there is more
> interest).  The data is backed up up across country nightly, then to
> tape, which is stored at a secure site.  20 days worth of backups are
> retained on immediate storage and 20 months worth on tape (at least
> until the storage needs to be upgraded).  The only requirement to use
> the site is: the software has to be available under an OSI approved
> license.
>
> If interested email me.
>
> Axton
> http://arswiki.org
>
> On 3/9/07, Watson, Benjamin A. <[EMAIL PROTECTED]> wrote:
>> Axton,
>>
>> Wanna stand up a Bugzilla portal off of your ARSWiki?
>>
>> I'd be glad to submit a list of RKM related bugs that I've uncovered 
>> and fixed.
>>
>> Ben
>>
>> ________________________________
>>
>> From: [EMAIL PROTECTED] on behalf of Carey Matthew Black
>> Sent: Fri 3/9/2007 10:31 AM
>> To: [email protected]
>> Subject: Re: Remedy Supported Products
>>
>>
>>
>> Roy,
>>
>> It has been my experience (not only of late, but for several years)
>> that the mantra of "support" is "send us your logs" and "use the
>> latest patch".
>>
>> The amount of support that they provide for anything except the most
>> current patch of the day is to answer questions with statements like:
>>
>> " That might be fixed in a later patch. Have you tried patch "x"
yet?"
>> OR
>> " What version of the software are you using?"
>>   (For the Nth time for the same support issue.)
>>
>> OR ( And this one is my favorite)
>>
>> " No that is not a bug. Yes the documentation says that, but the
>> actual design is not that. The bug is in the documentation."
>>   ( And they even say that when the functionality _changed_ between
>> Major versions and the docs still reflect the "old versions
>> behaviour". )
>>
>>
>> I am beginning to think that the community could benefit from using a
>> Bugzilla (or some other such bug tracking tool) that the whole
>> community could map to BMC bugs and publish to the whole community.
>> Sure it would be more work for us, but we might actually be able to
>> group evaluate a patch instead of having to suffer individually
>> through the same issues over and over again.
>>
>> -- 
>> Carey Matthew Black
>> Remedy Skilled Professional (RSP)
>> ARS = Action Request System(Remedy)
>>
>> Love, then teach
>> Solution = People + Process + Tools
>> Fast, Accurate, Cheap.... Pick two.
>>
>>
>>
>>
>> On 3/9/07, Ashcraft, Roy W. <[EMAIL PROTECTED]> wrote:
>> > **
>> >
>> >
>> > I opened a ticket with BMC yesterday over a problem we are having
with
>> > Mid-Tier 7.00.00 patch 2. The immediate response, which was 
>> expected, was to
>> > update to version 7.00.01 patch 1. I responded explaining the
business
>> > reasons why that is not feasible for our situation. I very quickly 
>> received
>> > a response indicating that in order for them to escalate this to 
>> engineering
>> > we would have to upgrade to the latest patch.
>> >
>> > Is BMC only supported the current patch release now and forswearing

>> all
>> > support for past products, no matter how recent?
>> >
>> > Roy Ashcraft
>> > Systems Analyst
>> > SAIC
>> > [EMAIL PROTECTED]
>> > (402) 293-5218
>>
>>
________________________________________________________________________
_______ 
>>
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
>> ARSlist:"Where the Answers Are"
>>
>>
>>
>>
________________________________________________________________________
_______ 
>>
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
>> ARSlist:"Where the Answers Are"
>>
>
>
________________________________________________________________________
_______ 
>
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> ARSlist:"Where the Answers Are"
>

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to