Mark,
I'm woefully behind on some mail so you might already have these
answers, but I didn't see one on the list.
On 03/09/2009, at 7:19 PM, Mark Struberg wrote:
1.)
I see a lot of 'open' Jiras hanging although they are already fixed.
In that case, please close them :)
Usually when working with Jira I use the following workflow:
* created
if I fix the bug, I set the status to
* resolved
and if I go on and release the plugin/module i set it to
* closed
Most times I (or the release manager) use bulk change to pick all
the jiras which went into the release and transit it to 'closed'
This way we can easily see what got shipped and what is still not
public.
We skip resolved, and instead rely on the version to determine when it
is public.
2.)
Jira has a feature to automatically scan SVN (or any other SCM) and
parse the commit messages for any Jira links. (e.g. SCM-493). With
this information Jira is able to list all commits directly to the
issue (example: [1])
We already write the Jira issue numbers into the commit msg, so why
didn't we yet enable this feature? Codehaus don't even has to
provide FishEye themselfs because atlassian is so kind to do it for
Apache projects.
Maybe all this has a reason, but I didn't find it quoted on the
list, so I'd be happy to hear about it.
We used to have this, but the Codehaus JIRA set up changed when they
integrated everything and we've never bothered worrying about putting
it back.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
