scid vs. story id
1 view
Skip to first unread message
mabotelh
Feb 10, 2009, 9:38:01 PM2/10/09
to eXPlainPMT Users
Any reason why we have scid vs story id? In other words, what gotchas
are there if I drop scid? :-D
With stories now moving between projects, scid would not be such a
good unique identifier anymore since it has to be unique in the scope
of the project.
Mauro
are there if I drop scid? :-D
With stories now moving between projects, scid would not be such a
good unique identifier anymore since it has to be unique in the scope
of the project.
Mauro
Mauro Botelho
Feb 12, 2009, 10:42:44 AM2/12/09
to explainp...@googlegroups.com
Forwarding to the list...
On Wed, Feb 11, 2009 at 10:19 AM, Mauro Botelho <mabo...@gmail.com> wrote:
The problem with scid is just that it could have been sc15 in one project and then will be sc 26 in another one. So any references to sc15 now will be broken :(This happened to us where we were mentioning sc ids in release notes for example.MauroOn Tue, Feb 10, 2009 at 10:11 PM, Andy Trommer <atro...@gmail.com> wrote:
story_id is the auto-increment pk. As you mentioned, since scid is scoped to the project, it makes a good, user-friendly ID for each story. I know that teams like the SCID because it's much more natural to talk about your SCID 1 instead of SC 55434. We have many hundreds of thousands of cards in our system here at Sabre. Considering that projects usually only have a couple hundred cards, it would get tedious using the story_id in all cases.
I'd say that you'd want to reset the SCID to the max(scid)+1 of the new project when you move a story in.
-Andy
--
Andy Trommer
atro...@gmail.com
Andy Trommer
Feb 10, 2009, 10:11:47 PM2/10/09
to explainp...@googlegroups.com
---------- Forwarded message ----------
From: Andy Trommer <atro...@gmail.com>
Date: Tue, Feb 10, 2009 at 9:11 PM
Subject: Re: scid vs. story id
To: mabotelh <mabo...@gmail.com>
story_id is the auto-increment pk. As you mentioned, since scid is scoped to the project, it makes a good, user-friendly ID for each story. I know that teams like the SCID because it's much more natural to talk about your SCID 1 instead of SC 55434. We have many hundreds of thousands of cards in our system here at Sabre. Considering that projects usually only have a couple hundred cards, it would get tedious using the story_id in all cases.
I'd say that you'd want to reset the SCID to the max(scid)+1 of the new project when you move a story in.
-Andy
From: Andy Trommer <atro...@gmail.com>
Date: Tue, Feb 10, 2009 at 9:11 PM
Subject: Re: scid vs. story id
To: mabotelh <mabo...@gmail.com>
story_id is the auto-increment pk. As you mentioned, since scid is scoped to the project, it makes a good, user-friendly ID for each story. I know that teams like the SCID because it's much more natural to talk about your SCID 1 instead of SC 55434. We have many hundreds of thousands of cards in our system here at Sabre. Considering that projects usually only have a couple hundred cards, it would get tedious using the story_id in all cases.
I'd say that you'd want to reset the SCID to the max(scid)+1 of the new project when you move a story in.
-Andy
On Tue, Feb 10, 2009 at 8:38 PM, mabotelh <mabo...@gmail.com> wrote:
--
Andy Trommer
atro...@gmail.com
Jake Dempsey
Feb 15, 2009, 10:51:34 PM2/15/09
to explainp...@googlegroups.com
I agree with Andy. Sabre has many thousand cards in a single install. I think the largest project I saw had 600 cards, and every team uses the term SCXX to discuss any given storycard. I would use an approach similar to what Andy describes when moving the stories.
Andy, Can you take lead on getting Mauro's changes back into the main trunk. I know he has made many improvements. It would be nice to re-baseline. I dont know if every change should go in, but we should evaluate each of them and apply them if they make sense for the main line.
Andy, Can you take lead on getting Mauro's changes back into the main trunk. I know he has made many improvements. It would be nice to re-baseline. I dont know if every change should go in, but we should evaluate each of them and apply them if they make sense for the main line.
Mauro Botelho
Feb 15, 2009, 10:57:11 PM2/15/09
to Jake Dempsey, explainp...@googlegroups.com
If there's a change you'd like to see improved in any way, please let me know. I'd be glad to adapt it.
Mauro
atrommer
Feb 16, 2009, 2:39:36 PM2/16/09
to eXPlainPMT Users
Sure thing.
Thanks for all the improvements, Mauro! I have them still in my fork
queue to review.
On Feb 15, 9:51 pm, Jake Dempsey <angelo0...@gmail.com> wrote:
> I agree with Andy. Sabre has many thousand cards in a single install. I
> think the largest project I saw had 600 cards, and every team uses the term
> SCXX to discuss any given storycard. I would use an approach similar to
> what Andy describes when moving the stories.
>
> Andy, Can you take lead on getting Mauro's changes back into the main
> trunk. I know he has made many improvements. It would be nice to
> re-baseline. I dont know if every change should go in, but we should
> evaluate each of them and apply them if they make sense for the main line.
>
Thanks for all the improvements, Mauro! I have them still in my fork
queue to review.
On Feb 15, 9:51 pm, Jake Dempsey <angelo0...@gmail.com> wrote:
> I agree with Andy. Sabre has many thousand cards in a single install. I
> think the largest project I saw had 600 cards, and every team uses the term
> SCXX to discuss any given storycard. I would use an approach similar to
> what Andy describes when moving the stories.
>
> Andy, Can you take lead on getting Mauro's changes back into the main
> trunk. I know he has made many improvements. It would be nice to
> re-baseline. I dont know if every change should go in, but we should
> evaluate each of them and apply them if they make sense for the main line.
>
> On Thu, Feb 12, 2009 at 9:42 AM, Mauro Botelho <mabot...@gmail.com> wrote:
> > Forwarding to the list...
>
> > Forwarding to the list...
>
> > On Wed, Feb 11, 2009 at 10:19 AM, Mauro Botelho <mabot...@gmail.com>wrote:
>
> >> The problem with scid is just that it could have been sc15 in one project
> >> and then will be sc 26 in another one. So any references to sc15 now will be
> >> broken :(
> >> This happened to us where we were mentioning sc ids in release notes for
> >> example.
>
> >> Mauro
>
>
> >> The problem with scid is just that it could have been sc15 in one project
> >> and then will be sc 26 in another one. So any references to sc15 now will be
> >> broken :(
> >> This happened to us where we were mentioning sc ids in release notes for
> >> example.
>
> >> Mauro
>
> >> On Tue, Feb 10, 2009 at 10:11 PM, Andy Trommer <atrom...@gmail.com>wrote:
>
> >>> story_id is the auto-increment pk. As you mentioned, since scid is scoped
> >>> to the project, it makes a good, user-friendly ID for each story. I know
> >>> that teams like the SCID because it's much more natural to talk about your
> >>> SCID 1 instead of SC 55434. We have many hundreds of thousands of cards in
> >>> our system here at Sabre. Considering that projects usually only have a
> >>> couple hundred cards, it would get tedious using the story_id in all cases.
>
> >>> I'd say that you'd want to reset the SCID to the max(scid)+1 of the new
> >>> project when you move a story in.
> >>> -Andy
>
>
> >>> story_id is the auto-increment pk. As you mentioned, since scid is scoped
> >>> to the project, it makes a good, user-friendly ID for each story. I know
> >>> that teams like the SCID because it's much more natural to talk about your
> >>> SCID 1 instead of SC 55434. We have many hundreds of thousands of cards in
> >>> our system here at Sabre. Considering that projects usually only have a
> >>> couple hundred cards, it would get tedious using the story_id in all cases.
>
> >>> I'd say that you'd want to reset the SCID to the max(scid)+1 of the new
> >>> project when you move a story in.
> >>> -Andy
>
> >>> On Tue, Feb 10, 2009 at 8:38 PM, mabotelh <mabot...@gmail.com> wrote:
>
> >>>> Any reason why we have scid vs story id? In other words, what gotchas
> >>>> are there if I drop scid? :-D
>
> >>>> With stories now moving between projects, scid would not be such a
> >>>> good unique identifier anymore since it has to be unique in the scope
> >>>> of the project.
>
> >>>> Mauro
>
> >>> --
> >>> Andy Trommer
> >>> atrom...@gmail.com>
> >>>> Any reason why we have scid vs story id? In other words, what gotchas
> >>>> are there if I drop scid? :-D
>
> >>>> With stories now moving between projects, scid would not be such a
> >>>> good unique identifier anymore since it has to be unique in the scope
> >>>> of the project.
>
> >>>> Mauro
>
> >>> --
> >>> Andy Trommer
Reply all
Reply to author
Forward
0 new messages