Re: Adding relationships: can be done in a fast way?

Use a format (/path/to/my/file:version) in the text box. No more, no less.
If you can make some extensions, you can make a custom validator (or even a
'choose files' adhoc screen) if you need it, so you are sure files really
exist, that you're not reporting several versions of the same file, and so
on...

Then, the task itself will hold the modified files, so your reporting system
("what files did get involved in solving this task?") is running in the
search box, and supported in the database.

(That said... people usually does it "the other way". Coders inform the Task
code in the commit message, and that's linked to the issue tracking
system...)

_
Jorge

On 11/14/07, Peña Palma, Alfredo <[email protected]> wrote:
>
>
>
>     The only problem is that the admin wants to associate the CVS version
> too, and generate reports so he can know what files (and what CVS version of
> them) are related to every issue or task. Is it possible to generate those
> reports without doing that way then? I hope so, the way we're working is
> much more than a 'real pain', trust me :)
>
>
> Thanks!
>
>
> ------------------------------
> *De:* Jorge Uriarte Aretxaga
> *Enviado el:* mié 14/11/2007 12:05
> *Para:* [email protected]
> *Asunto:* Re: Adding relationships: can be done in a fast way?
>
> So you'll eventually have every existing file registered in its own issue,
> related with any modification task on it during its life?
>
> Too verbose, and a real pain for the users. I don't think it'll scale.
>
> Why don't you use a text box to report involved files (one by line)?
> We've been doing some customization of that kind for some of our clients,
> so the repository (Subversion, CVS, FileSystem, whatever...) is tied to
> Scarab, including validation (make sure what you're filling in are really
> existing files), and reporting (what tasks have been done on each file?)
>
> Saludos,
>
> _
> Jorge
>
> On 11/14/07, Peña Palma, Alfredo <[email protected]> wrote:
> >
> >
> >
> >     Let's see: I create a new issue, and then I create one object
> > (issue) for every file involved in the resolution of the task.
> > Then I create an "is relationed with" relation in 'Related issues', so I
> > can know the files associated with that task, generate reports and so on.
> >     This way of working with issues has been proposed by the admin, but
> > I don't think it's a good way to go, since it's very annoying (and time
> > consuming) to create one issue for each file, and create the relation for
> > every one of them. That's why I'm asking for another approach :-)
> >
> >
> > Thanks!
> >
> >
> >
> > ------------------------------
> > *De:* Jorge Uriarte Aretxaga
> > *Enviado el:* mié 14/11/2007 11:31
> > *Para:* [email protected]
> > *Asunto:* Re: Adding relationships: can be done in a fast way?
> >
> >  Hola Alfredo;
> >
> > I don't get what you mean with "modifying 100 files".
> > Are you creating a new issuetype "file" ?
> > Or are you attaching 100 files to the task?
> >
> > You can always automate a complex task, but I'd like to understand what
> > you're trying to do.
> >
> > Regards,
> >
> > _
> > Jorge
> >
> > On 11/14/07, Peña Palma, Alfredo <mailto:[email protected]<[email protected]>>
> > wrote:
> > >
> > >
> > >    Hi! I'm using scarab for tracking issues and tasks, but I don't
> > > know if I'm using
> > > it the right way. For example, I created a task, that involved
> > > modifying 100 files.
> > > Now should I create those 100 objects manually, and then assign them
> > > to that task?
> > > That would take too much time... is there any other way to do it?
> > >
> > >
> > >
> > > Thanks!
> > >
> > >
> > >
> >
> >
>