William
06-26-2003, 07:19 PM
Question's at the bottom if you want to skip the tale of woe.
Here's the story: Company insists on using Vantive for CM for
mysterious reasons (probably because it's there). No one is
really happy with the interface, but for submitting change
requests it's usable if tedious. As a developer, I don't have
to create too many tickets, just change the status and send
them on, sometimes with a note.
However, I'm also the build master for several products and
subcomponents. That means, after a build, I have to deal with
a large batch of tickets that have to be opened, have their status
changed, a build number added, and then sent off to the
appropriate QA person. Based on a few tests, this involves a
dozen or so mouse clicks, some typing into two or three fields
(the inbox list has several hundred names in it, so forget an easy
drop-down and pick), plus the time spent waiting for the screen
to update. (It seems to be the worst blend of platform-specific
client and web-based app.)
Did I mention I'm in physical therapy for a pinched nerve that
adds just so much more entertainment value to the above?
Up until a few months ago I was using TeamTrack. Sure, it was
web based, but it was definitely faster to react. More importantly,
I set up a mass-transition report where I could list out all the build
candidate issues, check the boxes of the ones in the build, then,
by entering the build # once, update and dispatch them all.
So, the question: Is there something similar I can do with Vantive
to group issues, update them all at once, and dispatch them? (My
boss's suggestion is to use some kind of macro recorder, but that
seems pretty hacky and prone to error.) Thanks in advance. -Wm
wh@ij@un@k@@au@st@in@.r@r.@co@m
Here's the story: Company insists on using Vantive for CM for
mysterious reasons (probably because it's there). No one is
really happy with the interface, but for submitting change
requests it's usable if tedious. As a developer, I don't have
to create too many tickets, just change the status and send
them on, sometimes with a note.
However, I'm also the build master for several products and
subcomponents. That means, after a build, I have to deal with
a large batch of tickets that have to be opened, have their status
changed, a build number added, and then sent off to the
appropriate QA person. Based on a few tests, this involves a
dozen or so mouse clicks, some typing into two or three fields
(the inbox list has several hundred names in it, so forget an easy
drop-down and pick), plus the time spent waiting for the screen
to update. (It seems to be the worst blend of platform-specific
client and web-based app.)
Did I mention I'm in physical therapy for a pinched nerve that
adds just so much more entertainment value to the above?
Up until a few months ago I was using TeamTrack. Sure, it was
web based, but it was definitely faster to react. More importantly,
I set up a mass-transition report where I could list out all the build
candidate issues, check the boxes of the ones in the build, then,
by entering the build # once, update and dispatch them all.
So, the question: Is there something similar I can do with Vantive
to group issues, update them all at once, and dispatch them? (My
boss's suggestion is to use some kind of macro recorder, but that
seems pretty hacky and prone to error.) Thanks in advance. -Wm
wh@ij@un@k@@au@st@in@.r@r.@co@m