On Mar 1, 2014, at 2:10 AM, Peter von Kaehne <ref...@gmx.net> wrote:
> How do I mark an issue as resolved if it is long gone, but not marked as > so? > Just click on the "Resolve Issue" button, get the resolve screen, fill it out and submit it. > Do I need special rights and how do I get them? Hope not. If not, I can grant them. > > Example in point > > http://www.crosswire.org/tracker/browse/API-98 > > I checked the code and it is fixed. > > Or can one assume that bugs listed as affecting a past version are > resolved? Not really. That's the version when the problem was found. It might not be fixed. The field Fixed Version is for noting what release the fix was put in. > > If so, is there a process to bulk mark resolved all that are for past > versions? Yes. I've not used it, but it preferable to doing the same repetitious task. And it cuts down on the amount of mail I get. (I get one for each action in Jira.) I think it is done by performing a search and then applying a change to the entire search result. > > I am asking as I am one who has not made use of JIRA much so far. But > looking at 42 unresolved unassigned items for libsword is dispiriting - > until it became clear that not all of the 42 are actually still > relevant. I think that the tracker will become more useful. There has been a recent decided change where people have said that we should be posting patches in Jira. I think that is probably a very good way to collaborate. For JSword, we have all Jira issues going to the jsword-devel mailing list. This has helped to foster collaboration and tracking of changes. I'm at the end of my day, but I'll be glad to help tomorrow, if you need it. In Him, DM
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
