Ok THanks for your great work, Ricardo.
No someone needs to manage attached patches:) Best Regards, Alexander 2014-09-16 21:39 GMT+12:00 Oskar Berggren <oskar.bergg...@gmail.com>: > Yes, a single one is good. > > 2014-09-16 10:05 GMT+02:00 Ricardo Peres <rjpe...@gmail.com>: > >> Hi, >> >> As you may have noticed, I have been placing has-pull-request tags in all >> open issues that either have a pull request submitted or have a fix >> mentioned in the comments or even have an attached patch. IMO, having a >> single tag is preferable to having multiple - has-patch, has-fix, etc. >> What do you think? >> >> RP >> >> >> On Monday, August 25, 2014 9:50:30 PM UTC+1, Alexander Zaytsev wrote: >>> >>> You actually can add labels to JIRA issues automatically based on pull >>> requests, but it requires to modify workflow. >>> >>> >>> 2014-08-26 7:35 GMT+12:00 Ricardo Peres <rjp...@gmail.com>: >>> >>> Yeah, I thought so... hence my suggestion for a tag. But this requires >>>> that someone with admin rights on JIRA adds the tag as soon as there's a >>>> pull request. >>>> >>>> RP >>>> >>>> >>>> On Monday, August 25, 2014 7:51:25 PM UTC+1, Oskar Berggren wrote: >>>> >>>>> There seems to be no way to query for issues with pull requests in >>>>> Jira. So far I haven't seen it as a problem, since I've just looked at the >>>>> list of open pull requests in Git. >>>>> >>>>> /Oskar >>>>> >>>>> >>>>> 2014-08-25 14:24 GMT+02:00 Alexander Zaytsev <haz...@gmail.com>: >>>>> >>>>>> We don't >>>>>> >>>>>> Atlassin recently updated JIRA whci has some features about tracking >>>>>> pull request (via statuses), so probably we need to give it a go. >>>>>> >>>>>> Best Regards, >>>>>> Alexander >>>>>> >>>>>> >>>>>> 2014-08-26 0:20 GMT+12:00 Ricardo Peres <rjp...@gmail.com>: >>>>>> >>>>>> Guys, >>>>>>> >>>>>>> How do you currently track which issues have pull requests? >>>>>>> Why not use a tag "pull-request"? >>>>>>> >>>>>>> RP >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> --- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "nhibernate-development" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to nhibernate-development+unsubscr...@googlegroups.com >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "nhibernate-development" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to nhibernate-development+unsubscr...@googlegroups.com. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "nhibernate-development" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to nhibernate-development+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nhibernate-development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nhibernate-development+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nhibernate-development+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
