On Wed, Jun 6, 2018 at 1:29 PM Sanne Grinovero wrote:
> I don't know about others but I didn't make changes on JIRA in a long
> time - or I'd normally share actions here.
>
It might also be due to a JIRA upgrade as they did quite a lot of changes.
Anyway, we are back on track now.
--
Guillaum
On 6 June 2018 at 12:04, Guillaume Smet wrote:
> On Wed, Jun 6, 2018 at 12:57 PM Sanne Grinovero wrote:
>>
>> Just curious, did that really work consistently?
>
>
> Well, it works consistently as in if your issue is in the "Pull request
> sent" status, the issue is considered "In progress".
>
> T
On Wed, Jun 6, 2018 at 12:57 PM Sanne Grinovero wrote:
> Just curious, did that really work consistently?
>
Well, it works consistently as in if your issue is in the "Pull request
sent" status, the issue is considered "In progress".
This status is associated with the explicit action "Link to pu
Just curious, did that really work consistently?
As far as I know, the JIRA integration was never really able to match
GitHub PR changes to JIRA issues reliably.
On 6 June 2018 at 11:37, Guillaume Smet wrote:
> Hi,
>
> A few months back, when an issue was in the "Pull request sent" status, it
>
Nice! I had noticed that, but didn't think further, assuming it would not
be configurable anyway.
Thanks for fixing it.
On Wed, 6 Jun 2018 at 12:44 Guillaume Smet wrote:
> Hi,
>
> A few months back, when an issue was in the "Pull request sent" status, it
> was considered "In progress" and appear
Hi,
A few months back, when an issue was in the "Pull request sent" status, it
was considered "In progress" and appeared here:
https://hibernate.atlassian.net/projects/HV/versions/3/tab/release-report-in-progress
.
This apparently got broken at some point (or someone changed it without
asking
