From msoulier at digitaltorque.ca  Mon Jul 12 12:01:01 2010
From: msoulier at digitaltorque.ca (Michael P. Soulier)
Date: Mon, 12 Jul 2010 12:01:01 -0400
Subject: [ditz-talk] automation of ditz
Message-ID: <20100712160031.GF1144@digitaltorque.ca>

Hi,

I'm currently working in a mostly ClearCase/ClearQuest proprietary
environment, but mirroring my code into a Git repo so I can work on it offline
and use Git's tools, which are far superior.

I'm now looking at mirroring issues from CQ into ditz, as CQ has a perl api so
I could make it happen, but I'm unsure of how to automate creating issues.
ditz prompts interactively, is there a way to get it to take most args via
command-line switches, and maybe take the description on stdin?

I suppose I could write the issue files directly but I'm unsure of what I
would break by doing this.

Thanks,
Mike
-- 
Michael P. Soulier <msoulier at digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20100712/4221f3a1/attachment.bin>

From nate at natemurray.com  Mon Jul 12 12:31:33 2010
From: nate at natemurray.com (Nate Murray)
Date: Mon, 12 Jul 2010 09:31:33 -0700
Subject: [ditz-talk] automation of ditz
In-Reply-To: <20100712160031.GF1144@digitaltorque.ca>
References: <20100712160031.GF1144@digitaltorque.ca>
Message-ID: <AANLkTimO7P4OaaXjcHuOL_6N6YX7YEPwtRNjYG_gzcwX@mail.gmail.com>

I started a ditz plugin for interacting with jira a while back. I only
finished it to the point for downloading tickets but not creating
them.

However, you might find some of the code useful:
http://github.com/jashmenn/ditz-jira

Nate


On Mon, Jul 12, 2010 at 9:01 AM, Michael P. Soulier
<msoulier at digitaltorque.ca> wrote:
> Hi,
>
> I'm currently working in a mostly ClearCase/ClearQuest proprietary
> environment, but mirroring my code into a Git repo so I can work on it offline
> and use Git's tools, which are far superior.
>
> I'm now looking at mirroring issues from CQ into ditz, as CQ has a perl api so
> I could make it happen, but I'm unsure of how to automate creating issues.
> ditz prompts interactively, is there a way to get it to take most args via
> command-line switches, and maybe take the description on stdin?
>
> I suppose I could write the issue files directly but I'm unsure of what I
> would break by doing this.
>
> Thanks,
> Mike
> --
> Michael P. Soulier <msoulier at digitaltorque.ca>
> "Any intelligent fool can make things bigger and more complex... It takes a
> touch of genius - and a lot of courage to move in the opposite direction."
> --Albert Einstein
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkw7PB8ACgkQKGqCc1vIvgixNACfRAPv2F3CpjiGc0z99ghHV6TA
> Z6sAn2+TVkl2rTsqtmRgMR8UOfwaWH16
> =D9ml
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> ditz-talk mailing list
> ditz-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ditz-talk
>
>

From msoulier at digitaltorque.ca  Mon Jul 12 21:07:14 2010
From: msoulier at digitaltorque.ca (Michael P. Soulier)
Date: Mon, 12 Jul 2010 21:07:14 -0400
Subject: [ditz-talk] automation of ditz
In-Reply-To: <AANLkTimO7P4OaaXjcHuOL_6N6YX7YEPwtRNjYG_gzcwX@mail.gmail.com>
References: <20100712160031.GF1144@digitaltorque.ca>
	<AANLkTimO7P4OaaXjcHuOL_6N6YX7YEPwtRNjYG_gzcwX@mail.gmail.com>
Message-ID: <20100713010713.GK21394@anton.digitaltorque.ca>

On 12/07/10 Nate Murray said:

> I started a ditz plugin for interacting with jira a while back. I only
> finished it to the point for downloading tickets but not creating
> them.
> 
> However, you might find some of the code useful:
> http://github.com/jashmenn/ditz-jira

Thanks, I'll take a look. Given the cqperl interface I think I'll use perl
though.

Mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20100712/a07fa0d5/attachment.bin>

From seanerussell at gmail.com  Tue Jul 13 06:09:28 2010
From: seanerussell at gmail.com (Sean Russell)
Date: Tue, 13 Jul 2010 06:09:28 -0400
Subject: [ditz-talk] automation of ditz
In-Reply-To: <20100713010713.GK21394@anton.digitaltorque.ca>
References: <20100712160031.GF1144@digitaltorque.ca>
	<AANLkTimO7P4OaaXjcHuOL_6N6YX7YEPwtRNjYG_gzcwX@mail.gmail.com>
	<20100713010713.GK21394@anton.digitaltorque.ca>
Message-ID: <AANLkTilVYjGOy-Bf4eGbBD9FHtpSYCAHId7mmuqnN-2g@mail.gmail.com>

I have a project for syncing ditz with trac.  It does bi-directional
syncing.  Given that ditz is Ruby, the plug-in is in Ruby as well:

http://trac.germane-software.com/ditz-trac

--- SER

On Mon, Jul 12, 2010 at 9:07 PM, Michael P. Soulier <
msoulier at digitaltorque.ca> wrote:

> On 12/07/10 Nate Murray said:
>
> > I started a ditz plugin for interacting with jira a while back. I only
> > finished it to the point for downloading tickets but not creating
> > them.
> >
> > However, you might find some of the code useful:
> > http://github.com/jashmenn/ditz-jira
>
> Thanks, I'll take a look. Given the cqperl interface I think I'll use perl
> though.
>
> Mike
>
> _______________________________________________
> ditz-talk mailing list
> ditz-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ditz-talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20100713/c236b481/attachment.html>

From msoulier at digitaltorque.ca  Tue Jul 20 16:02:48 2010
From: msoulier at digitaltorque.ca (Michael P. Soulier)
Date: Tue, 20 Jul 2010 16:02:48 -0400
Subject: [ditz-talk] viewing all issues
Message-ID: <20100720200245.GB19773@digitaltorque.ca>

Hi,

How do I create a list of all issues, sorted by status (open, closed), so that
I can go back and easily view closed items?

I don't see a way beyond looking at the files themselves.

BTW, love the html status pages. That's awesome.

Mike
-- 
Michael P. Soulier <msoulier at digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://rubyforge.org/pipermail/ditz-talk/attachments/20100720/29f590c4/attachment.bin>

From garethpriede at gmail.com  Wed Jul 21 16:02:59 2010
From: garethpriede at gmail.com ('Gareth Priede')
Date: Wed, 21 Jul 2010 22:02:59 +0200
Subject: [ditz-talk] A sundry list of ad-hoc features I've added
Message-ID: <87d3ug8ux8.wl%gtp@implicitdesign.co.za>


Hi,

I thought I'd list some of the changes I've made to my repo of
ditz. I've mangled the original code a bit which is why I haven't
tried to get them pushed to the main repo, but in case someone finds
these useful, get hold of me or clone the ploppy branch.

My work environment is working solo or with one other developer. I
often have to communicate my issues list with a client, so most of
these things revolve around getting that information out.

- IDs. The guid ids are irritating because they're hard to refer to
  and they change. So I added an option to .ditz-config called
  sha_name. If this option is sha then the existing guid functionality
  is enabled. If it is anything else, and I typically use 'g' as my
  initial, then guids are generated in the format
  <sha_name><some_number>, so for example g21.

  This id is unique as long as everyone adding to ditz chooses a
  unique initial. In a controlled environment this isn't hard to
  enforce. 

  The number part is 1 plus the count of all the issues, so it's
  guaranteed to be unique on your machine, and by concatenating the
  unique initial it's unique across all machines.

- Made org-mode prettier. I changed some colours to make things
  easier, and added some shortcuts like 'Edit the actual file' which
  takes you to the .yaml file.

- Linking from emacs org-mode. I have a shortcut which copies the ditz
  link from an emacs buffer which can then be posted into org as a
  link. The link opens the ditz-mode viewing the ditz issue
  content. The 't' shortcut then links back to the ditz-todo list.

- ditz-time-release function. As an alternative to ditz-todo, shows a
  more comprehensive list of issues in a slightly different format. 

  The first part of the output looks like this:

	Sprint6 (unreleased):
	[time taken = 11.0 (estimated would take 19.6 hours)]
	[estimates are too high by 56.1224489795918%]
	[estimated time left = 10.9 hours. adjusted time is 6.11734693877551 hours]

	Change requests based on Sprint5

	_ g97 : g97 : dev_done : (took 0.017 hours by gtp, estimate 0.3 hours) remove admin viewing of case classification categories
	_ g98 : g98 : dev_done : (took 2.9 hours by gtp, estimate 2 hours) fix scores
	_ g101 : g101 : dev_done : (took 0.133 hours by gtp, estimate 0.4 hours) move the 'dont include R symbol' somewhere else
	_ g107 : g107 : dev_done : (took 0.017 hours by gtp, estimate 0.2 hours) remove hr tag from referral to service provider first tab

  It includes:
  - estimated time for all open releases
  - comparison of estimated time with real time for closed issues.
  - estimated time for all issues
  - actual time for all closed issues
  - the name of the person who closed the issue.

- Added ditz spec command, which creates an overview page in html and
  rtf. This contains content which can be cut-and-pasted into a Word
  doc, with a small bit of reformatting required to neaten it
  up. Contains the usual stuff like issues and releases, but in a more
  tabulated format. This part is particularly hacky, because I also
  convert my org-mode mockup files to html, which is outside the
  regular ditz-as-an-issue-manager scope.

gtp