If you prefer to mark resolved at the time of closing the PR, that's fine (I probably won't be doing that because I consider it a useless step - there're enough fields/states in JIRA that get ignored as is), but you should still track down the owner and make sure it ends up closed.

In short, if you want to add an extra work for yourself, fine, but it's not required and I probably won't be doing it unless we start to see some value in doing so :)

On Fri, Jan 16, 2015 at 11:54 AM, Ondrej Zizka <ozizka@redhat.com> wrote:

+1. Also - if unsure, how about Resolving and asking to close? I think that's what that state is supposed to be for, or at least we can use it that way.

Ondra
On 16.1.2015 01:11, Lincoln Baxter, III wrote:
Better yet. If it's unclear if there's more work, actually ask if the issue is closed. Use common sense here. If you're not sure if it's done, have a conversation. But the point is. We have WAY too many issues open in JIRA that are actually fixed or finished. We can do better.

On Thu, Jan 15, 2015 at 6:20 PM, Lincoln Baxter, III <lincoln@redhat.com> wrote:

If you merge a pull request, also close the related issue and make sure the Fix Version and Assignee fields are set.

Thanks guys,
--
Lincoln Baxter, III
JBoss, by Red Hat
lbaxter@redhat.com

"If you want something, you'll find a way; if you don't, you'll find an excuse."

_______________________________________________
windup-dev mailing list
windup-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev

--

Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing list
windup-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev

Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."