You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by Greg Hill <gr...@RACKSPACE.COM> on 2016/01/14 18:04:41 UTC
[dev] Closing JIRAs
I have a few open JIRAs that have been fixed, but the JIRA status was never updated. Am I just supposed to update the JIRA? I assumed some automation would take care of it.
Greg
Re: [dev] Closing JIRAs
Posted by Tomaz Muraus <to...@apache.org>.
Actually, I could be wrong about automation, maybe it needs to be closed
manually.
On Thu, Jan 14, 2016 at 6:16 PM, Greg Hill <gr...@rackspace.com> wrote:
> https://issues.apache.org/jira/browse/LIBCLOUD-682 is an example. I did
> reference the JIRA in the commit message, but maybe I needed to add a
> #resolves tag or something?
>
>
> Greg
>
> On 1/14/16, 11:14 AM, "Tomaz Muraus" <to...@apache.org> wrote:
>
> >In theory, AFAIK, if the pull request references JIRA issue number in the
> >title, the issue should get closed when the pull request is closed /
> >merged.
> >
> >If that doesn't happen, it needs to be done manually. If you have created
> >the issue yourself, I believe you should be able to mark it resolved as
> >well.
> >
> >If that's not the case, please let us know.
> >
> >On Thu, Jan 14, 2016 at 6:04 PM, Greg Hill <gr...@rackspace.com>
> >wrote:
> >
> >> I have a few open JIRAs that have been fixed, but the JIRA status was
> >> never updated. Am I just supposed to update the JIRA? I assumed some
> >> automation would take care of it.
> >>
> >> Greg
> >>
> >>
>
>
Re: [dev] Closing JIRAs
Posted by Greg Hill <gr...@RACKSPACE.COM>.
https://issues.apache.org/jira/browse/LIBCLOUD-682 is an example. I did
reference the JIRA in the commit message, but maybe I needed to add a
#resolves tag or something?
Greg
On 1/14/16, 11:14 AM, "Tomaz Muraus" <to...@apache.org> wrote:
>In theory, AFAIK, if the pull request references JIRA issue number in the
>title, the issue should get closed when the pull request is closed /
>merged.
>
>If that doesn't happen, it needs to be done manually. If you have created
>the issue yourself, I believe you should be able to mark it resolved as
>well.
>
>If that's not the case, please let us know.
>
>On Thu, Jan 14, 2016 at 6:04 PM, Greg Hill <gr...@rackspace.com>
>wrote:
>
>> I have a few open JIRAs that have been fixed, but the JIRA status was
>> never updated. Am I just supposed to update the JIRA? I assumed some
>> automation would take care of it.
>>
>> Greg
>>
>>
Re: [dev] Closing JIRAs
Posted by Tomaz Muraus <to...@apache.org>.
In theory, AFAIK, if the pull request references JIRA issue number in the
title, the issue should get closed when the pull request is closed / merged.
If that doesn't happen, it needs to be done manually. If you have created
the issue yourself, I believe you should be able to mark it resolved as
well.
If that's not the case, please let us know.
On Thu, Jan 14, 2016 at 6:04 PM, Greg Hill <gr...@rackspace.com> wrote:
> I have a few open JIRAs that have been fixed, but the JIRA status was
> never updated. Am I just supposed to update the JIRA? I assumed some
> automation would take care of it.
>
> Greg
>
>