Talk about battle of the exaggerations! :)
Generally speaking, I prefer not to have multiple issues: if you
put attachments and comments and stuff on one, or even edit it to change
the description entirely, any "matching" issues are unafected. The "link"
is pretty minor in the UI. This could result in two issues that are
supposed to be the same inadvertently leading to totally different changes
in two branches or whatever.
That said, if branches are divergent enough that the same solution
does not work even if the problem is the same, I suppose I would be in
favor of separate issues. I suspect this would be true of 1.3 vs 5.6.
Aaron
On Wed, 20 Jul 2005, David Jencks wrote:
> > +1000
> >
> > I feel pretty strongly about this. Is there some big problem that
> > would cause us to split an issue across several Jira entries?
> well,
> -1000
>
> I feel pretty strongly about this too. Obviously its better to fix
> stuff in all branches at once, but it won't always be possible,
> especially after 1.3 diverges from 1.0, 2.4 vs 1.1, 5.6 vs 2.1 etc. At
> some point you have to say that there are different issues in different
> branches, even though the symptom is the same. I think the jira guys
> know of what they speak when the recommend using multiple entries.
>
> david jencks
>
>
