You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Robert Burke <ro...@frantil.com> on 2020/08/01 00:30:28 UTC

Re: [BROKEN] Please add "Fix Version" when resolving or closing Jiras

Just confirming that we're still seeing Status:Resolved ; Resolution:
Unresolved.

I tried finding a way to change the Resolution field but there was no way
to do so. Everything else lets me edit it, but not that field.

On Fri, Jul 24, 2020, 11:21 AM Kenneth Knowles <ke...@apache.org> wrote:

> I've noticed that when status == Resolved and Resolution == Unresolved,
> subtasks are not given the green checkmark of doneness. Just noting another
> quality-of-life issue caused here.
>
> Kenn
>
> On Thu, Jul 23, 2020 at 4:09 PM Brian Hulette <bh...@google.com> wrote:
>
>> +1 - I think I saw somewhere Resolved is intended for "this is fixed"
>> while Closed is "the reporter/some authority has verified it's fixed".
>> Doesn't seem to apply to us.
>>
>> On Thu, Jul 23, 2020 at 2:21 PM Kyle Weaver <kc...@google.com> wrote:
>>
>>> > we could simplify those to a single state and let the Resolution field
>>> be the one source of truth for the nature of the resolution.
>>>
>>> +1
>>>
>>> On Thu, Jul 23, 2020 at 2:14 PM Kenneth Knowles <ke...@apache.org> wrote:
>>>
>>>> This is unfortunate :-(
>>>>
>>>> Also unfortunate: I have just enough permissions to mess it up and not
>>>> enough to fix it. You can follow
>>>> https://issues.apache.org/jira/browse/INFRA-20563
>>>>
>>>> By the way, does anyone really use the difference between "Resolved"
>>>> and "Closed"? Since I am talking to Infra and probably getting our workflow
>>>> re-initialized manually, we could simplify those to a single state and let
>>>> the Resolution field be the one source of truth for the nature of the
>>>> resolution. (typically I think fixed things get "resolved" while wontfix
>>>> issues get "closed" - this is not actually what the difference is supposed
>>>> to be)
>>>>
>>>> Kenn
>>>>
>>>> On Thu, Jul 23, 2020 at 9:43 AM Brian Hulette <bh...@google.com>
>>>> wrote:
>>>>
>>>>> Yeah same for me. Not a huge deal.. I just noticed that the jira UI
>>>>> isn't rendering references to my closed tickets with a strikethrough, and
>>>>> I'd like to distinguish others as "won't fix" or "obsolete". It should be
>>>>> easy enough to backfill these once this is sorted out though.
>>>>>
>>>>> Brian
>>>>>
>>>>> On Thu, Jul 23, 2020 at 2:01 AM Maximilian Michels <mx...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I can close/resolve but it will show "Resolution: Unresolved":
>>>>>>
>>>>>> On 23.07.20 02:30, Brian Hulette wrote:
>>>>>>
>>>>>> Is setting the Resolution broken as well? I realized I've been
>>>>>> closing jiras with Resolution "Unresolved" and I can't actually change it
>>>>>> to "Fixed".
>>>>>>
>>>>>> On Tue, Jul 21, 2020 at 7:19 AM Maximilian Michels <mx...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Also, a friendly reminder to always close the JIRA issue after
>>>>>>> merging a
>>>>>>> fix. It's easy to forget.
>>>>>>>
>>>>>>> On 20.07.20 21:04, Kenneth Knowles wrote:
>>>>>>> > Hi all,
>>>>>>> >
>>>>>>> > In working on our Jira automation, I've messed up our Jira
>>>>>>> workflow. It
>>>>>>> > will no longer prompt you to fill in "Fix Version" when you
>>>>>>> resolve or
>>>>>>> > close an issue. I will be working with infra to restore this. In
>>>>>>> the
>>>>>>> > meantime, please try to remember to add a Fix Version to each
>>>>>>> issue that
>>>>>>> > you close, so that we get automated detailed release notes.
>>>>>>> >
>>>>>>> > Kenn
>>>>>>>
>>>>>>