The resolved/closed question is interesting. I guess they could be
resolved, but reviewed and closed by the release manager. Otherwise,
I'd agree that they seem to function the same for open source projects
anyways.
Don
Brett Porter wrote:
We actually eliminated the resolve step since weren't using it
independantly of resolve, however this doesn't affect the other part.
I'm not exactly sure of the technical details of how we made editing
possible when it was resolved/closed - but I can find out. It doesn't
actually transition to any different steps in between.
Cheers,
Brett
On 4/27/06, Don Brown <[EMAIL PROTECTED]> wrote:
What does the end workflow look like? Do you just add a transition to resolve
to the close step?
Don
Brett Porter wrote:
Hi,
I've noticed that there have been 1 or 2 mails recently on this list
to reopen and close jira issues. Am I correct in assuming this is to
be able to edit the fix version or other details?
If this will be a regular occurrence, I recommend working with the
jira admins to create a custom workflow. We've done that in Maven and
it allows you to edit issues that are closed with appropriate
permissions. It's a big timesaver if used responsibly.
just my $A0.02
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
