> I also struggle to see the value of a "no longer valid" field. We would
> cover such a think in (our company) JIRA by using the "Won't Fix" or similar
> resolution along with an explanatory comment.
The point is that only members of the development team can change the
status and resolution of an issue. Allowing anyone to do it would (in
my view) undermine JIRA for us.
The "no longer valid" field is a hint to the development team that the
issue can probably be closed. It's also something that can be easily
searched on.
> The value of "Last reviewed date" depends on how you work with JIRA. If you
> tend to review bugs but not actually modify the issue, then it could be of
> value to set this. However I would suggest that if you've taken the time to
> review a bug it might be better to make that little extra effort to take an
> action, such as add a comment suggesting a solution or way forward, or
> perhaps reschedule the "fixed in" version to a general estimate, or even a
> comment saying "sounds valid but we certainly can't look at this before
> version 2.1 - maybe someone can contribute" or whatever. In any case if you
> update _something_ on the issue then the issue will reflect those changes
> and thereby actually indicates the "last reviewed" via the "updated date"
> field. The filter on "Last reviewed date" is of course an interesting idea,
> and obviously different to filtering on "updated date" because it only takes
> into account changes by the team, not updates by anyone.
> Sorry, I didn't set out to put down your suggestions. As said it really
> depends on how you like to work with JIRA.
The "last reviewed date" is purely for members of the community so
that they can help out with checking old JIRAs without going over a
bunch of issues that were reviewed recently by someone else. Yes, a
comment is nice but it's complete pain to search on. With the last
reviewed date, it's dead simple to set up a query to show those issues
that haven't be reviewed in a while.
> Another question on this matter - can a contributor relax in the knowledge
> that GIT pull requests will all get assessed in due course, or is it worth
> "making some noise"? (not that I have any outstanding, just wondering)
Feel free to make some noise. Sometimes they get missed. Sometimes
someone has looked at them, but hasn't added anything to the comments.
Ideally, all pull requests would be reviewed within 7 days and some
statement of intent added in a comment.
Peter
--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Locked
