I don't know if it makes any practical difference, but I wonder if we
should decide to use either "Resolved" or "Closed", but not both.
Right now, we seem to be using either/or, willy-nilly.
Following up on Don's observations, my preferences would be to keep it
simple and just use Resolved and for
The problem is that there is no real way for the reporter to evaluate it.
Yeah, you can go build the snapshot, but that would be a very dedicated
reporter. If we setup nightly snapshots of Struts, I think perhaps, you
could have a purpose between Resolved vs. Closed.
Paul
On 8/9/07, Antonio Petre
2007/8/9, Dale Newfield <[EMAIL PROTECTED]>:
> Does JIRA send email to the reporter when the issue is marked resolved?
Yes
> If we could just alter that email to encourage them to re-evaluate and
> close...
>
> ...but I agree there's not a huge up side to that.
This kind of collaboration is ve
Ted Husted wrote:
As Don mentioned, a closed status is useful when there are two
distinct groups handling the same ticket, since ti tells us that the
second group signed-off. But, since we don't have that kind of
workflow, I don't see any practical reason for us to use closed.
Well, we could en
+1 from me
--
James Mitchell
On Aug 9, 2007, at 10:18 AM, Ted Husted wrote:
On 8/9/07, Jeff Turner <[EMAIL PROTECTED]> wrote:
Let me know if the Struts devs prefer to keep Closed issues
uneditable.
+1 for editing.
Thanks Jeff!
--
On 8/9/07, Jeff Turner <[EMAIL PROTECTED]> wrote:
> Let me know if the Struts devs prefer to keep Closed issues uneditable.
+1 for editing.
Thanks Jeff!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
Speaking as a RM, unless there is a clear technical advantage that
saves us work in some way, I don't see the point in adding yet-another
step to the process. As Don mentioned, a closed status is useful when
there are two distinct groups handling the same ticket, since ti tells
us that the second g
2007/8/9, Paul Benedict <[EMAIL PROTECTED]>:
>
> Would anyone find it valuable to remove either Resolved or Closed? Is that
> even possible? I don't object to getting rid of one. What do you think Don
> and Antonio?
I don't know...
The concept of "close when it's released" it's useful: if you se
Would anyone find it valuable to remove either Resolved or Closed? Is that
even possible? I don't object to getting rid of one. What do you think Don
and Antonio?
On 8/9/07, Jeff Turner <[EMAIL PROTECTED]> wrote:
>
> On Thu, Aug 09, 2007 at 03:32:43PM +1000, Don Brown wrote:
> > I believe the trad
On Thu, Aug 09, 2007 at 03:32:43PM +1000, Don Brown wrote:
> I believe the traditional purpose of the "closed" state is for a QA
> department, so they can mark the issues they have verified to be
> fixed. In Struts, I don't think we really do that, and while we do
> informal code reviews (commit e
I believe the traditional purpose of the "closed" state is for a QA
department, so they can mark the issues they have verified to be
fixed. In Struts, I don't think we really do that, and while we do
informal code reviews (commit emails), we certainly don't require
formal test documents that verif
According to JIRA:
*Resolved = *A resolution has been taken, and it is awaiting verification by
reporter. From here issues are either reopened, or are closed.
***Closed = *The issue is considered finished, the resolution is correct.
Issues which are not closed can be reopened.
That seems pretty pr
Is there any practical advantage to closing a resolved issue after a release?
On 8/7/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> Don, the PITA truth is the only reason why I use Resolved up to a release.
> :-)
>
> On 8/7/07, Don Brown <[EMAIL PROTECTED]> wrote:
> >
> > My 2c is I don't see any
Don, the PITA truth is the only reason why I use Resolved up to a release.
:-)
On 8/7/07, Don Brown <[EMAIL PROTECTED]> wrote:
>
> My 2c is I don't see any practical value in resolved/closed. They are
> functionally the same thing, only closed is a PITA because to change
> it, you have to reopen
My 2c is I don't see any practical value in resolved/closed. They are
functionally the same thing, only closed is a PITA because to change
it, you have to reopen it. I know many orgs have workflows where the
two states mean very different things, but for Struts, I think it
would be overkill.
Sti
I have been doing the same: resolving when finishing the issue and then
closing once the release is finished.
On 8/7/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> On 8/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> > 2007/8/7, James Mitchell <[EMAIL PROTECTED]>:
> > >
> > > That makes se
On 8/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> 2007/8/7, James Mitchell <[EMAIL PROTECTED]>:
> >
> > That makes sense to me. I don't remember what the decision was on
> > that. I think this has more to do with making the release managers
> > life easier than policy per se.
> >
> > I can
2007/8/7, James Mitchell <[EMAIL PROTECTED]>:
>
> That makes sense to me. I don't remember what the decision was on
> that. I think this has more to do with making the release managers
> life easier than policy per se.
>
> I can reopen and resolve if needed.
It wasn't an "accusation" for your p
That makes sense to me. I don't remember what the decision was on
that. I think this has more to do with making the release managers
life easier than policy per se.
I can reopen and resolve if needed.
--
James Mitchell
On Aug 7, 2007, at 10:03 AM, Antonio Petrelli wrote:
Hi all!
Just
Hi all!
Just a (maybe stupid) question: what is the policy about
resolving/closing issues?
At Tiles, we resolve issues when we finish committing, and close them
once a vote has been positive for a release.
Thoughts?
Antonio
-
To
20 matches
Mail list logo
